I installed the BDE on the network, now the proble is whenever I try to create a distribution package and select the runtime files it also include the BDE. The install programs now overwrites the previous install of the BDE. 1)Can the runtime files be installed on the network or does it have to be locally distributed? 2)If Locally distributed, how can I prevent the BDE from being selected? 3)If I do an uninstall it removes the BDE from the network, unchecking the uninstall feature only prevents the registry entries from being removed, can this be blocked? 4)Where can I find out which files are included in the runtime files so I can use install shield instead of the the distribution expert and also which ones should be registered.
If this is your account, sign in to activate web presence data (sign in quarterly to keep active). Alternatively, you can subscribe to our monthly eMag with a valid email address.
Web Presence Hidden.
Once above is taken care of, full Profile content will display including back links, about me, my message, custom Profile html,
social networking links, message board signature, company profile, etc.
Paradox and BDE actually run on each computer accessing the network tables so you have to install Paradox and the BDE on each machine. Although each machine could install to the network, most installation I've seen install it locally.
Just heard from a member via a private message so I thought I would add the result of that email here just for completeness:
As I indicated above, all files can reside on the network but you still have registry and other settings to setup on each client computer. Since most installations these days are just a few PCs, I think it might be easier to just use existing installers to get things running. You'll have to make up you're own mind but the question is does the buessiness expense justify the time spent.
If you decide you do want to create your own installer in order to setup each computer, Steven Green sent me a link to a nice Bill Todd article where he gives an example:
To be clear, you don't really share the BDE on the network, you simply use the network as a file server that shares files over the network to each computer. Each computer still loads all files into memory and runs them locally. Although Borland has always recommended installing the BDE (and Paradox) on each computer, it's really up to you.
This can be a useful technique if you ever need to update the BDE (not likely at this point) and the update is just a matter of replacing a few files with no local computer changes needed. With this setup, you replace the files in one location on the network. Pretty handy.
Oh, also, almost forgot. Since the BDE isn't really being shared, the only sharing going on is as a file server then each user/computer would still load up the BDE exactly as if it were isntalled locally which is good because then you have full access to the full assets of the BDE just as if it were isntalled locally (for example, each computer has a full 48 sessions available).
Paradox
Print This
