Conflict between VFP and FOXPROW

[Pollock]

I have a client running a 16 bit foxprow for windows application and a visual foxpro 6.0 sp5 application on the same machine, and I was wondering if anybody has ever come across problems with the two conflicting with each other. The client is experience wierd word errors, problems with the foxprow getting divide by zero errors and not properly saving information. The vfp app was just installed in the last month.

 

[DSummZZZ]

Are they accessing common tables?
You shouldn't have any problems unless the VFP app tries to change the table structure, like with PACK or ALTER TABLE or something.
As long as you have things like service packs and network clients current, it shoud be fine.



-Dave S.-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Pollock]

No, not accessing or sharing, it almost seems like a memory conflict.

 

[rgbean]

I agree with Dave, you shouldn't have any problems.

Have you applied the High Speed CPU patch to FPW2.6a? What MEMLIMIT settings are you using in the FPW CONFIG.FPW file?

Rick

 

[Pollock]

No they have been running the 16 bit for about 5 years

 

[rgbean]

Does the "Divide by Zero" happen at startup of the FPW app, or just before/during/after printing? The first means that you are probably running on a CPU faster than ~133 Mhz and haven't applied the patch. The second usually means that you need switch printer drivers or add some reset the floating point processor code!

Rick

 

[Pollock]

No actually the divide by zero error occurs when they are in the 16 bit program.