BDE error: Invalid File Name

Scott A. Duman

unread,

Dec 1, 1998, 3:00:00 AM12/1/98

to

I have a customer that recently bought a new computer and tried to
install one of our products (which they were previously using on an
older workstation). When they start up the application, they get the
following message:

Application Error: Exception EDB Engine Error in module
ServiceTool.exe at 0005d620
Invalid File Name

If they install the same software, using the same disks on the old
computer, it runs without a problem.

The new computer with the error is a Gateway E-3200 PentiumPro running
Windows 95 4.000.950b.

Any ideas???

Thanks,

Scott Duman
Mark Systems

Alex Soto

unread,

Dec 1, 1998, 3:00:00 AM12/1/98

to

Check in the new machine's "Control Panel/Regional Settings" what
language the machine is set to. It is set to the same language as the
older machine?

Alex Soto

Jeff Overcash

unread,

Dec 1, 1998, 3:00:00 AM12/1/98

to

If it's a D2 app the problem is probably that the new machine has FAT32
disks and he has a BDE version before 3.51f. The solution ias to either
do not put db files on any paths that have spaces or long filenames or
upgrade to a bde version that is 3.51f or later.

Jeff Overcash

Bill Todd (TeamB)

unread,

Dec 1, 1998, 3:00:00 AM12/1/98

to

What version of the BDE is your app using? The new computer probably uses
the FAT32 file system. You must have BDE 3.5 with the FAT32 patch or later
to use FAT32.

--
Bill Todd
(Sorry but TeamB cannot answer questions received via email)
(Remove nospam from my email address to contact me for any other reason)

Scott A. Duman

unread,

Dec 3, 1998, 3:00:00 AM12/3/98

to

Scott A. Duman wrote:
>
> I have a customer that recently bought a new computer and tried to
> install one of our products (which they were previously using on an
> older workstation). When they start up the application, they get the
> following message:
>
> Application Error: Exception EDB Engine Error in module
> ServiceTool.exe at 0005d620
> Invalid File Name
>
> If they install the same software, using the same disks on the old
> computer, it runs without a problem.
>
> The new computer with the error is a Gateway E-3200 PentiumPro running
> Windows 95 4.000.950b.
>
> Any ideas???
>
> Thanks,
>
> Scott Duman
> Mark Systems

I have IDAPI32.dll Version 3.5.0.21 on my computer (right click >
properties > Version Tab) with Local Disk (FAT 32) showing on my C:
DRIVE Properties. I have other workstations that have the same version
IDAPI32.dll and just Local Disk showing for their C: Drive Properties.
Both work fine.

1) Is the Disk properties the correct place to check to if the system
is FAT32?

2) Am I checking the right place for the BDE version (IDAPI32.dll
properties)?

3) Does 3.5.0.21 have the FAT32 patch (since it works on both
workstations here)

Brian Bushay TeamB

unread,

Dec 4, 1998, 3:00:00 AM12/4/98

to

>
>1) Is the Disk properties the correct place to check to if the system
>is FAT32?

Yes

>
>2) Am I checking the right place for the BDE version (IDAPI32.dll
>properties)?

Yes

>
>3) Does 3.5.0.21 have the FAT32 patch (since it works on both
>workstations here)

I can't remember the exact version number. Basically only the BDE 3.5 that was
in the original version of Delphi 2 had a fat32 problem. Borland got out a
patch very quickly after the problem was discovered.
If your BDE version works on a fat32 drier it is the patched version

--
Brian Bushay (TeamB)
Bbu...@NMPLS.com