FoxPro outputs .err.filename files

[robmazco]

OK, Im the go-between so I may not have all the answers and this may not make sense.

A user has a test and live foxpro 9 environment. Both are setup EXACTLY alike as near as he can tell. Hes pretty snappy with foxpro so Im trusting his info.
They run from the TEST environment a report they created which outputs files correctly to our subsidiary off-site. It correctly creates the txt files off-site with name filename.xxx.
When running the exact same setup on the LIVE environment, it creates the same txt files BUT locally and with name .err.filename.xxx.
It wont output the files off-site and it adds the .err. in front of filename when running in LIVE, it works perfect in TEST.

Ideas?

 

[Olaf Doschke]

err, um, maybe take that program to a speech therapist.

Typically there's only one place foxpro creates a filename with an .err fileextension: when you compile something and errors are in the code, but I've not had something createing a prefix .err., I doubt the reson is a fox bug or foxpro specific, it should be specificly from your code.

Well, first idea: debug. Without further infos I can't give you any advice. Reports generating files with some extension, hmmm. fox rerports? reportlisteners? word docs, using some third party product like xfrx or frx2any or do you print pdfs? Is some printer driver involved? It could be so manyfold reasons, I rather stop enumerating them until you can tell more about the code generating those files.

Bye, Olaf.

 

[robmazco]

thnx Olaf, I know its vague but alas, Im not the foxpro user. He asked if I could look into it with the info he gave me.
And the only thing I know about foxpro is how to install it for the users...

 

[Olaf Doschke]

I understand you're not the programmer, sorry I can't help you further. All I can tell is that hasn't happend to me from foxpro in about 10 years usage of VFP6 to 9, so I'm rather sure the reason is not within foxpro, might be reasons outside his program, eg network, firewall, tcp port, eg errors in creating that file remote as it seems to be intended lead in the file being created local with this prefix, perhaps even by intention.

Bye, Olaf.

 

[robmazco]

ack...
Turns out he was misdirecting the output on the LIVE environment.
Test was pointing to a Dev site
Live was pointing to a Dev01 site, dev01 site doesnt exist.
He changed the LIVE to point to Dev site, works perfect now.