[DUG] Paradox and TclientDataSet Delphi 2005 Install Express
BDEmerge modules
Paul A Norman
paul.a.norman at gmail.com
Thu Nov 3 17:07:25 NZDT 2005
Thanks Todd,
It actually never occured to me! blerrrr . . really obvious.
Here is the link to the Merge Module for BDE 5.11 if any one ever is
looking to it found it by googling the Borland.com <http://Borland.com>site.
http://info.borland.com/devsupport/bde/bdeupdate.html
On 03/11/05, Todd Martin <toddm at kol.co.nz> wrote:
>
> If you start your application in the Delphi IDE and then open View->Debug
> Windows->Modules (Ctrl-Alt-M) you will see all the packages/dlls loaded by
> your application. That will give you a check list of what to deploy.
> If you add "MidasLib" to your unit uses clause, you will find "Midas.dll"
> is not loaded.
> Todd.
>
> ----- Original Message -----
> *From:* Paul A Norman <paul.a.norman at gmail.com>
> *To:* NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
> *Sent:* Thursday, November 03, 2005 9:13 AM
> *Subject:* Re: [DUG] Paradox and TclientDataSet Delphi 2005 Install
> Express BDEmerge modules
>
> Thanks Jeremy, does it matter which unit, I placed it in my primary
> datamodule.
> This is what got me thinking I should include the dll,
>
> (ms-
> help://borland.bds3/bds3win32devguide/html/dapdeployingdatabaseapplications
> )
> "Database applications that use client datasets such as *TClientDataSet*or dataset providers require you to include
> midaslib.dcu (for static linking when providing a stand-alone executable);
> if you are packaging your application (with the executable and any needed
> DLLs), you need to include Midas.dll."
>
> Midas.dll normally lives in the windows / system32 it seems.
> And re including the BDE in my installs
>
> (ms-
> help://borland.bds3/bds3win32devguide/html/dapborlanddatabaseengine.htm)
> "You should use InstallShield Express (or other certified installation
> program) for installing the BDE. InstallShield Express creates the necessary
> registry entries and defines any aliases the application may require."
>
> But the distributed InstallShield Express does not have the necessary
> merge modules readily available. BDE does not even show as a merge module
> and the appropriate directories are empty!
> I tried searching Borland for "BDE" but came up with only three or four
> entries none of them relevent.
> I realised last night that this is the first app in D2005 I was trying to
> deploy that wasn't using MySql or simple text files. Everything else had
> been maintenece or extension in D4 Pro as some components I have are not
> D2005 or .pas available.
> Amyone had to deploy BDE from D2005?
> Paul
>
> On 03/11/05, Jeremy North <jeremy.north at gmail.com> wrote:
> >
> > If you add the MidasLib unit to the uses clause of a unit in your
> > application you don't have to worry about distributing midas.dll
> >
> > cheers,
> > Jeremy
> >
> > >I am aware I should include the
> > > Midas.dll and inclued the .DCU, any thing important about where the
> > > midas.dll goes win/system32 or in App. directrory?
> >
> > _______________________________________________
> > Delphi mailing list
> > Delphi at ns3.123.co.nz
> > http://ns3.123.co.nz/mailman/listinfo/delphi
> >
>
> ------------------------------
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
> ------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.361 / Virus Database: 267.12.6/151 - Release Date: 28/10/2005
>
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns3.123.co.nz/pipermail/delphi/attachments/20051103/edfce6bd/attachment.html
More information about the Delphi
mailing list