Fox Pro

**Irish Shark** · March 18th, 2005, 03:46 PM

Hi All,

Have a client using a Fox Pro database program from a mapped drive. The program runs a setup which establishes a node to the client. All computers that were on the system used Win98SE without any problems. My issue is that upon integration of a Win2k workstation, I get the following error upon starting the program:

Devide By Zero or Overflow Error

I think that I need to add an enviromental variable or two, can anyone point me in the correct direction?

Thanks

**geoscomp** · March 18th, 2005, 04:07 PM

The "Divide by Zero" error usually happens on an older Fox version running on a newer PC or operating system. There is a Microsoft supported patch for that but you need to be at version 2.6a before you apply the patch. i don't know what version you are running, but, here's the references:

microsofts article

divide by zero

**Ya_know** · March 18th, 2005, 04:22 PM

What's the actual program and version information? Do they have a website, and still support this version? The first place I'd look is for support from the manufacturer, I would have to believe this is either a known issue they may have resolved in their Knowlege Base...

Out of curiosity, what lead you to believe you required additional variables?

**Irish Shark** · March 19th, 2005, 02:53 AM

Originally Posted by Ya_know

What's the actual program and version information? Do they have a website, and still support this version? The first place I'd look is for support from the manufacturer, I would have to believe this is either a known issue they may have resolved in their Knowlege Base...

Out of curiosity, what lead you to believe you required additional variables?

I thought of variables due to a simular Dbase problem with Win2k and a DOS based Dbase program. I will check the web site of the program manufacture and post back.

**confus-ed** · March 19th, 2005, 08:43 AM

Originally Posted by Irish Shark

I thought of variables due to a simular Dbase problem with Win2k and a DOS based Dbase program...

Yeah you get these, due to 'local scope', as Dos sessions are beyond it & without setting global variables you can't get it to work, as the information is 'inside' a dos session & can't get out properly to windows to be 'serviced' otherwise (win 98 etc are 'just dos with pictures'

).

I'd have thought though that Geoscomp has 'nailed it' ? here, with his answer ?

**GHSTECH** · March 19th, 2005, 11:56 PM

I have seen this issue before, try lowering your screen resolution and/or color depth. I know it sounds weird, but it worked for us.

**Irish Shark** · March 20th, 2005, 11:58 PM

Manufacture web site states that I need to replace the "FOXW2600.ESL" file in the global directory of the database. I will try this tommorrow and post back.

**Irish Shark** · March 21st, 2005, 04:16 PM

Originally Posted by Irish Shark

Manufacture web site states that I need to replace the "FOXW2600.ESL" file in the global directory of the database. I will try this tommorrow and post back.

Well that did not work, manufacture web site lists the fix for a newer version of the software. Will recomend to client that they got their moneys worth out of the current version. Thanks for the help.

**geoscomp** · March 21st, 2005, 04:21 PM

Just out of curiosity, did you try those two patches I posted? I've used those on a few foxpro networks around here with success

**Irish Shark** · March 21st, 2005, 04:23 PM

Originally Posted by Irish Shark

Manufacture web site states that I need to replace the "FOXW2600.ESL" file in the global directory of the database. I will try this tommorrow and post back.

Well that did not work, manufacture web site lists the fix for a newer version of the software. Will recomend to client that they got their moneys worth out of the current version. Thanks for the help.