🚀 go-pugleaf

First, the C++Builder executables *are* runtime versions. The
things you probably experienced are missing the set of system
files, like:

   borlndmm.dll
   cc3260mt.dll
   rtl60.bpl
   etc...

The more VCL functionality (packages) your include, the more
system files you'll need. There are couple of things you can do:

First, you can force all the necessary system files to be linked to
your executable:

UNCHECK: Project/Options/Linker/Use Dunamic RTL
UNCHECK: Project/Options/Packages/Build with runtime packages

That will make your EXE much bigger, and I do not like this way. The
bad news is that this does not work for 3rd party components if you
used them.

The second thing you can do is to find out what DLL & BPL are
needed (execute on a neutral machine), and include them with
your exe. Place them in the same folder where your exe resides, or
in the OS system folder ('system32' at xp, ans 'system' at 98).

Also you can make your automated install procedure by using the
InstallShield (Express), or some other (probably free) app.



-- 
Best regards,
Vladimir Stefanovic
"DKalling" <dkalling@cnx2.com> wrote in message 
news:420cf996$1@newsgroups.borland.com...
> Obviously, I am a novice at using Borland Builder C++ (Visual). I have 
> developed an application for WIndows SQL using Builder v6 and in order to 
> make the program run on another system, I have had to install the entire 
> Builder Package on that machine. I am obviously overlooking something. 
> What I desire of course, is that when I compile my application(s) that I 
> can move a copy of it to any other desktop and execute the program. (All 
> systems in-house are running Win/XP). Some advice and guidance will be 
> greatly appreciated.
>
> Thanks in advance. Dave Kalling (dkalling@cnx2.com)
> 

Vladimir,

Thank you for your response, and it is much appreciated.

I have essentially tried all of the steps in your second option below 
(attempting to run my application on a new computer system) and I copied 
each of the dll & bpl files that were indicated as being missing into 
the same directory as my exe. Once I had gotten all the way thru this 
process however, and tried once again to launch the application, I 
received an error message indicating that the Borland Database engine 
could not be started. What step is needed in order to get the engine 
started on this system?

Thanks again for your help.

Dave Kalling

Vladimir Stefanovic wrote:
> First, the C++Builder executables *are* runtime versions. The
> things you probably experienced are missing the set of system
> files, like:
> 
>    borlndmm.dll
>    cc3260mt.dll
>    rtl60.bpl
>    etc...
> 
> The more VCL functionality (packages) your include, the more
> system files you'll need. There are couple of things you can do:
> 
> First, you can force all the necessary system files to be linked to
> your executable:
> 
> UNCHECK: Project/Options/Linker/Use Dunamic RTL
> UNCHECK: Project/Options/Packages/Build with runtime packages
> 
> That will make your EXE much bigger, and I do not like this way. The
> bad news is that this does not work for 3rd party components if you
> used them.
> 
> The second thing you can do is to find out what DLL & BPL are
> needed (execute on a neutral machine), and include them with
> your exe. Place them in the same folder where your exe resides, or
> in the OS system folder ('system32' at xp, ans 'system' at 98).
> 
> Also you can make your automated install procedure by using the
> InstallShield (Express), or some other (probably free) app.
> 
> 
> 

The variety of un-perfect ways of how to install BDE,
because my app needs it was one of the reasons I
abandoned BDE. I use ADO now, and I'm happy.

I remember the app (google for it)
bdeinfosetup.exe
...which will be enough for you.

Also look at:
http://www.jrsoftware.org/iskb.php?a=bde

Alternatively, you can use the installshield which was
distributed with BCB5 (not 6) and you can make your
blank app with only BDE selected.

Anyway, I suggest you ADO!

-- 
Best regards,
Vladimir Stefanovic
"DKalling" <dkalling@cnx2.com> wrote in message 
news:420f7a88$1@newsgroups.borland.com...
> Vladimir,
>
> Thank you for your response, and it is much appreciated.
>
> I have essentially tried all of the steps in your second option below 
> (attempting to run my application on a new computer system) and I copied 
> each of the dll & bpl files that were indicated as being missing into the 
> same directory as my exe. Once I had gotten all the way thru this process 
> however, and tried once again to launch the application, I received an 
> error message indicating that the Borland Database engine could not be 
> started. What step is needed in order to get the engine started on this 
> system?
>
> Thanks again for your help.
>
> Dave Kalling
>
> Vladimir Stefanovic wrote:
>> First, the C++Builder executables *are* runtime versions. The
>> things you probably experienced are missing the set of system
>> files, like:
>>
>>    borlndmm.dll
>>    cc3260mt.dll
>>    rtl60.bpl
>>    etc...
>>
>> The more VCL functionality (packages) your include, the more
>> system files you'll need. There are couple of things you can do:
>>
>> First, you can force all the necessary system files to be linked to
>> your executable:
>>
>> UNCHECK: Project/Options/Linker/Use Dunamic RTL
>> UNCHECK: Project/Options/Packages/Build with runtime packages
>>
>> That will make your EXE much bigger, and I do not like this way. The
>> bad news is that this does not work for 3rd party components if you
>> used them.
>>
>> The second thing you can do is to find out what DLL & BPL are
>> needed (execute on a neutral machine), and include them with
>> your exe. Place them in the same folder where your exe resides, or
>> in the OS system folder ('system32' at xp, ans 'system' at 98).
>>
>> Also you can make your automated install procedure by using the
>> InstallShield (Express), or some other (probably free) app.
>>
>>
>>
>