> No, we are literallt writing to the file, not even using the old 2.x memvar trick.. So, if a user decides he doesn't like what he has entered, he has to change it back.. The thing I am going on about is, that forms I had thought and everywhere else that deals with Data sessions didn't really have to track them and pass them around as part of the process (as parameters for a form, or a report)..
>
>I am have read a few books on developing in VFP, and looked at a framework or two (Am looking to maybe settle on Visual FoxExpress), but it's hard when the database design is so bad, that you can't use the features of the language that you are working in..
>.
>
>Sorry for the ranting, but with the people I work with, it seems like they either don't get it, or they really don't give a damn..

Tony,

It sounds like this project is a real dog. If you have any choice in the matter perhaps you shouldn't do it. The client (or whoever) is dicticating a non-normalized database. That is crazy.

You will work on this, and then you will be associated with this thing when it crashes, is hard to maintain, etc...

It might not be worth your damaging your reputation working on this project. If you are obliged to work on it. Sit down with the client, your boss (or whoever) and give the straight goods to them. The product won't work for long and it will be hard to maintain.

Sorry for the rant, but this is what I would do.