Help! BDE Issues

[LWB]

I'm really very BDE ignorant. I don't understand it at all and it keeps getting me in trouble!

After deciding to wait a bit on doing the Runtime 7 to 10 conversion (software running fine in Paradox 10, but the installation software sounds like considerable effort is required), I've run into some problems with InstallShield Express (that ships with Paradox 7). And I'm confused about BDEs in general.

First issue: I have Paradox 7 and 8 (and 10) running on my computer. The BDE is version 5.11 (or 5.1.1). However when I run my application in Paradox 7 it assumes that a date entered as 98 is 2098 while Paradox 8 assumes that it is 1998. I thought this was a change between an older and newer BDE. This is running the same program from the same working directory.

Second issue: I Created an Installation disk with my application (delivered versions of the files above) and the same BDE on it. I installed it on another computer that had no Paradox or BDE on it. The dates I entered as two digits stayed two digits, while on the other computer the always converted to 4 digits.

When I used the BDE Admin tool, both computers had the 4 digit date set to False and changing it had no impact (after closing and restarting Paradox).

Third issue: The original BDE with Install Shield includes a file called IDAPI32.CNF that was in the BDE/IDAPI CNF File group. The location of this file is in the InstallShield directory, not the BDE directory (as were the original IDAPINST.DLL & CTL3D32). I did include it in the install, but all the other BDE files have been updated with the newer BDE files. What is this file? I've been the including IDAPI.cfg that I am currently using.

And I was hoping not to run into stuff like this prior to making the jump to Paradox Runtime 10!

Lynn

 

[footpad]

Lynn,

I haven't used InstallShield Express for some time, so I'll need to either find some time for research or defer to someone with more recent knowledge regarding the CNF file.

You may find the following links helpful as well:

--

http://www.thedbcommunity.com/faq/12.htm

--

http://community.borland.com/article/0,1410,18727,00.html)

--

http://www.bdesupport.com/deploy.htm

(It looks like there are some changes you'll need to make to the installation script created by ISX, as BDE has changed since the version you're using was originally released.)

As far as the handling of two digit years goes, use the BDE Administrator to check the System | Formats | Date settings. There should be one called YEARBIASED that is either TRUE or FALSE. When TRUE, is adds 1900 to two digit years.

If you don't have the setting, then it needs to be added to the Registry.

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE   Borland\Database Engine\Settings\SYSTEM\FORMATS\DATE

(Be aware that you need should exit ALL BDE client applications, include BDE Admin, before modifying the Registry. You should also make a backup of the Registry before tweaking it. (For details, please see

http://techtricks.com/assorted/regbackup.php3)

As far as the four digit year data entry goes, I have always handle this using pictures on my field objects or similar client side programming, primarily because I didn't want to modify the behavior of all BDE applications for my own development preferences.

Hope this helps...

-- Lance

 

[LWB]

Lance,

Thanks for the advice. I read the links, the description of using InstallShield Express to install Runtime gets scary when it gets into Delphi scripts.

The Paradox 7 InstallShield Express has groups of files (application, Runtime, and 3 different BDE groups). It also has a section of Registry Keys that I have never touched and don't really understand.

I was just replacing the original BDE files with the BDE 5 files in the groups that matched. And I'm still installing Paradox 7 Runtime. Would I be better off just letting the user (which normally are not very computer literate) install with the original BDE and then have them run the BDE updates to get the BDE 5 installed.

Of course that is a two step process - which I was trying to avoid. I was hoping to save some work for myself this time, by not jumping to Paradox Runtime 10 (which would be a two step process unless I get InstallShield or Wise or something to do the installation).

I assume the database installer for Runtime 10 does install the BDE also. And then the user would just have to copy the application files to the appropriate directory? Or am I missing something?

I have to get this figured out by the end of this week!

Lynn

 

[Langley]

The runtime install does include the BDE files. Application files can then be copied seperately; or, you can use the PDE and deliver the application and runtime installation at the same time. I have heard some negative comments about the PDE but I have used it exclusively for several years without problems.

Mac

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us

 

[LWB]

Mac,

I thought that Paradox 10 didn't come with the PDE. Only with Paradox 9 Developer's Edition. I don't own Paradox 9 - Only 7, Runtime 7, Paradox 8, Runtime 8, Paradox 10 (from Corel Office 2000) and Runtime 10 (downloaded).

I wouldn't mind having the Paradox 9 Developers Edition, but they are impossible to find now! Will the Paradox 9 PDE work with Paradox 10? I thought I read somewhere that it would not. There were a couple of recommendations - Wise and Inno (?) as distribution options.

Lynn

 

[footpad]

Lynn,

Sorry for the delay in replying.

No, the Paradox 9 PDE will not work with Paradox 10, as the PDE uses delivered Paradox documents. As you probably know, delivered documents need to be compiled for use with the version of PAradox you're actually using.

It's too bad Corel didn't offer a more helpful upgrade path for those using the PDE, but there it is.

Also, you may be able to find Paradox 9 Dev Edition on one of the auction sites.

BTW, I found several hits for Paradox 9 Developer's Edition on froggle (

http://froogle.com).

Search for "Paradox 9" Developer (use the quotes). You'll have to scroll through the matches to find one, but I saw several when I ran that query this morning.

Hope this helps...

-- Lance

 

[LWB]

Lance,

That's interesting that the PDE (Paradox Runtime 9) only works with delivered documents. That is not the case for InstallShield Express (Paradox Runtime 7) - at least I have included both delivered and undeliver forms and reports without a problem. I have InstallShield Express correctly installing a current BDE (although it insists that the IDAPI32.CNF file be included, but I don't think it is used). So it appears that I should be able to get InstallShield Express to work with Paradox Runtime 10 installations (without using Delphi scripts). I think I should be able to place the Paradox 10 runtime files in the group that currently contains the Paradox 7 runtime files.

I will have to give that a try.

Lynn