![]() You may also need to permission the default BDE folder, so that users can reconfigure such things for other Paradox apps (God help them.), although I believe the location for the CFG can be configured by a registry setting: I ran out of time to research that further before deployment time. The application will create the PDOXUSRS.NET file in that location if none exists. If you are (or the vendor is) using the BDE merge module, you'll need to copy or merge the resulting CFG file in the MST, too. (Tools/Macro/Record Macro) Then while recording a macro, I went through the word document completing a mail merge manually. Make changes, if necessary, particularly to the netdir (CAN NOT reside in c: root under Vista), and save. Do NOT use the Control Panel icon to start the BDE Admin Open configuration on that cfg you copied. Set the folder to somewhere where users will have write access (IIRC, we used \Application Data\Borland\BDE - which we created in our MST) then save the configuration file. So basically you need to open Word, then under the Tools menu youll find a macro option,then under that youll see Record Macro. Start the BDE Admin by going to the bde directory in Windows Exploder, and right-clicking - as Administrator. Somewhere in there (I can't recall the exact detail) you need to configure the 'Native' Paradox driver's 'NET FILE' parameter. ![]() ![]() Use the file BDEADMIN.EXE in the Borland common files folder (by default, 'C:\Program Files\Common Files\Borland\BDE'). Unfortunately my vendor installation instructions aren't very clearShock! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |