﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <description><![CDATA[Comments for Deploying Applications that use ClientDataSets]]></description>
    <title><![CDATA[Comments for Deploying Applications that use ClientDataSets]]></title>
    <link>http://dn.codegear.com/article/29297</link>
    <!-- source: http://dn.codegear.com/article/29297/feed-->
    <dc:date>2008-11-21T14:10:57-08:00</dc:date>
    <item>
      <description><![CDATA[Does anyone can tell me how to statically link midas in Kylix, and please if it is no problem to contact me on my mail Kristijan.Horvat@iCodeTeam.net]]></description>
      <title><![CDATA[re: Yet another warning about NOT using midas.dll]]></title>
      <managingEditor>
	 (Kristijan Horvat)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=37448</guid>
      <dc:date>2004-08-19T21:16:15-07:00</dc:date>
      <pubDate>2004-08-19T21:16:15-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[I noticed, that it is not possible to use midas.dll in the following situation:Imagine an application compiled with runtime packages consisting of anEXE and a DLL. The DLL is dynamically loaded and unloaded using WinAPI calls LoadLibrary and FreeLibrary. If the DLL uses for example an TClientDataSet, then midas.dll is dynamically loaded by the VCL.If the application specific DLL is unloaded, midas.dll is also unloaded.The problem now is, that when the application specific DLL is loaded fora second time, then the VCL doesn't load midas.dll again (why?). This leads toaccess violations.In such a situation you should link unit midaslib to the EXE (simply add midaslib in the uses clause of the Delphi project of the EXE).]]></description>
      <title><![CDATA[Yet another warning about NOT using midas.dll]]></title>
      <managingEditor>
	 (Riccardo P. Foschia)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=35479</guid>
      <dc:date>2003-10-07T05:59:34-07:00</dc:date>
      <pubDate>2003-10-07T05:59:34-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[Hello, I would like to know how to statically link MidasLib ina C++ Builder 6 Enterprise application?Thanksodair.jc@terra.com.br]]></description>
      <title><![CDATA[What about using MidasLib in C++ Builder?]]></title>
      <managingEditor>
	 (Odair Custodio)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33773</guid>
      <dc:date>2002-12-19T11:34:26-08:00</dc:date>
      <pubDate>2002-12-19T11:34:26-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[Delphi dbExpress Help:"Crtl, MidasLibRequired by dbExpress executables that use client datasets such as TSQLClientDataSet"and:"dbExpIntApplications connecting to InterBase databases"What about Crtl unit???When I use dbExpInt My TFMTBCDField is truncated or raise.In my DBGrid Currency column is showed:Wrong values:$ ?.00$ 15.00$ ?.00$ =.00Correct values:$ 3.00$ 15.00$ 2.00$ 1.00]]></description>
      <title><![CDATA[Other Uses]]></title>
      <managingEditor>
	 (Cesar Romero)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33660</guid>
      <dc:date>2002-12-02T07:44:49-08:00</dc:date>
      <pubDate>2002-12-02T07:44:49-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[Following sentence (from article) is wrong:===================Under Linux, shared libraries are not shared in memory. Eachinstance of the library is loaded into its own process. (They are    called shared libraries because two or more applications can share the same file on disk.) As a result, this same savings in RAM is not realized when two or more Kylix applications that use ClientDataSets are running simultaneously.=================== DLL in Linux can not have a personal memory pool (not connected to any process) as (i think) in Windows, but commot pages of DLL (which not change itself) are shared among processes. Result: we _have_ saving of RAM under Linux.]]></description>
      <title><![CDATA[About DLL in Linux]]></title>
      <managingEditor>
	 (Sergey Korshunoff)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33649</guid>
      <dc:date>2002-11-29T19:03:40-08:00</dc:date>
      <pubDate>2002-11-29T19:03:40-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[I have found a lot of problems where client datasets are closed from the finalization code of a project: access violations and the like... So, I have adquired the good habit of explicitly destroying client datasets (and, indeed, existing forms data modules) before reaching the DPR file's end. This is VERY important for ISAPI applications using WebBroker and WebSnap.]]></description>
      <title><![CDATA[Another MIDAS trick]]></title>
      <managingEditor>
	 (Ian Marteens)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33645</guid>
      <dc:date>2002-11-28T23:44:49-08:00</dc:date>
      <pubDate>2002-11-28T23:44:49-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[However, you must be careful when linking midaslib.dcu to your application. First versions of Delphi 6 included different versions of the Midas code for the DLL and the embedded version. So, when you saved a cds to an XML file, you got different file formats: one of them used AttributeName, and the other FieldName, for column values. I think this was solved in Delphi 6.02.]]></description>
      <title><![CDATA[One warning about NOT using midas.dll]]></title>
      <managingEditor>
	 (Ian Marteens)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33644</guid>
      <dc:date>2002-11-28T23:39:23-08:00</dc:date>
      <pubDate>2002-11-28T23:39:23-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <item>
      <description><![CDATA[There is another disadvantage, when you use midas.dll instead of MidasLib. The first time, midas.dll is loaded on a machine, it automatically creates a registry entry with its path. From then, Windows always tries to load it from that path, so it will not find midas.dll any more, when you move it to another direcotry (e.g. on a shared network drive), because this path goes to the "local machine" registry.]]></description>
      <title><![CDATA[Another disadvantage of midas.dll]]></title>
      <managingEditor>
	 (Christian Kaufmann)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33629</guid>
      <dc:date>2002-11-27T05:58:50-08:00</dc:date>
      <pubDate>2002-11-27T05:58:50-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29297/feed">Comments for Deploying Applications that use ClientDataSets</source>
    </item>
    <generator>Atom 1.0 XSLT Transform v1 (http://atom.geekhood.net)</generator>
  </channel>
</rss>