Thanks for the quote. When we revamp the ported app using all OOP and a nice new framework (probably Drew Speedie's Visual MaxFrame Professional) we will certainly replace all these browse commands throughout the system.

I will use the quote to hammer the last browse thoughts from the client's mind. (I already told them this, but it helps having it in a published book. Real experts are from more than 50 miles away and have a briefcase. If they wrote a book .... !!!) ;-)

But, for now, I have to live with the browses. (Gag!) So, if possible, I have to find a work around.

This is not your typical database query app with lots of simple field display and little code snippets here and there. Just getting it from 2.6 to VFP 6 and running is a major effort. The code base has about $1,000,000 invested in it. So "just rewrite it" would have a little $500,000 price tag at best. That is not an option, as you may imagine.

It is always fun dealing with applications that have both accounting and government regulations involved. Throw in patients, insurance, employers, Medicare, durable medical equipment, diagnostics, medical procedures, co-pay, patient guarantor relationships, Provider (physician) location and patient relationships and electronic interaction with ERN and Electronic Submission...
There is a lot of logic in all of the 200 forms, not to mention the hundreds of reports, data transmission file input/output....

But, we are nearing completion. Because this was written using Tom Reddig's TRO layer, we have been able to add database containers and are adding transaction processing in the TRO layer. If it had not been for the late Tom Reddig, this "port" would not have been possible.

Now, if I can just get these browses to work... :-(

Thanks!