I am working on a reindex/pack/rebuildDBC type handler and have run up against the situation whereby a 'variable invalid' message is automatically displayed by FoxPro (vers 8) upon issueing a USE command for a table where the CDX tags contain references that are indeed invalid. The whole purpose of the reindex is to fix the problems and I don't need a user to see anything at all here - I am going to recreate the index. Since all the tables are part of a container I would very much prefer not to have to remove table/free table/reindex/add table all the time. For a single table that actually has a problem that is fine and expected. But if the only way to avoid the 'automatic messages' is to assume every index you are about to open might cause this issue and therefore go through the 'remove/free/reindex/add' routine would cause major slowdowns. It's a bloated way to solve the problem.

I don't want FoxPro to display messages - I want errors to trap. How can I create an auto reindex routine that runs at night, for example, if FoxPro is going to decide all on it's own to display information without at least giving me the opportunity to trap an error and provide a solution????

To recreate take any two tables and simply switch their CDX files (i.e., rename the CDX's to each other). Then try to open one of the tables in the command window. You get a message - no error to trap - announcing each 'invalid variable' and have to press OK on each. I want those messages to DIE! I've even tried setting the _SCREEN visible to false and the various/obvious SET commands off to no avail. They just keep coming up.

Hopefully, someone has run up against this and has figured out the hidden switch to stop these types of messages from automatically being thrown by FoxPro. I see no references to these messages in any help anywhere...

I've got my own idea of a work around but would prefer not to have to go there. I shouldn't have to.

Thanks in advance for your thoughts!


Steve