A free table keeps damaging

[lordhawkins]

I've got a new version from an old programa that has been running smoothly for the three last years, calculating production from Mon to Sat. It's called ACBH. Recently I've modified it to use data from Sunday. To play safe I've put the new version and the copies of the tables in other folder. It's is called ACBH2

The problem is, the free table, with the SAME structure is constantly damaged. The only operative difference is that ACBH2 is called from a Shell of VB. But the progam is the same old VFP routine.

What may be damaging the table?

 

[audiopro]

[i]constantly damaged[/i]

Corrupted or incorrect data?

Keith

http://www.studiosoft.co.uk

 

[lordhawkins]

I suppose the header is corrupted. Founding my assumption in an attemp to open it in OpenOffice 2.0. Got a text file with the data comma delimited, but the worksheet could not open it as rows and columns.

Any ideas?

 

[Mike Lewis]

Have you tried making a fresh copy, and storing it in a different location -- ideally, on a different drive, if available? That would help localise the cause of the problem.

Also, you said:

the worksheet could not open it as rows and columns.

Were you trying to open the file in a spreadsheet program? I don't know Open Office, but in Excel, that would only work if you had created the table in Fox 2.x or earlier, or copied the recent version to TYPE FOX2X.

If you created your copy simply by copying it within VFP, it will be a Visual Foxpro table, even though the original was from an earlier version.

I don't suppose that helps much, but worth keeping in mind perhaps.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[lordhawkins]

In fact, I've made a copy from the structure from the running copy, thru VFP. I assume that- no matter if I deploy it as a free table - it uses the VFP header.

When tryng to take a look inside the file, used OpenOffice and Excel, but both of them gave me errors. BTW, a .dbf can be open with Excel, no matter what version.

I've run it twice in this day, and no problem yet...

Let's see what is at day's end