We are using OECGI2. The return from OI contains correct data, but once we get to check it in the JavaScript, there is a message SYS1301 Table was not found in volume rec table list. What causes this message, where is it coming from. We are attaching the correct company data with each call to OI.

The SYS1301 message appears on the server console after the OECGI2 procedure finishes, correct?

Do all of your queries result in the SYS1301 message? If so, you may have a bad DBT file or perhaps a table name conflict. Does the DBT file reference a table that is getting attached dynamically?

Does the /INET_TRACE query result in the SYS1301 message?

My queries all get the SYS1301 message. I will check the dbt. The INET_TRACE does not result in the same message.

Any other ideas?

How did you determine OI is returning the correct information?

Where does the SYS1301 message appear?

If you try to access a routine in the EXAMPLES application by reconfiguring OECGI2 does the error still appear?

I look at the message being returned by OI right before the return. It is fine. Then in the Javascript I look at the message being returned. It contains the SYS1301.

Is it possible that this is a 'side-effect' of some function or stored procedure you're calling somewhere in your processing? Perhaps if you issued a SET_STATUS(0) before returning to clear out any error status that might exist, you would see a different result?

Thanks so much - That fixed it!

Much appreciated

Well that masked the error that is occuring somewhere. It would still be a good idea to track down the error. This fixes it in the same way that disabling the debugger stops people seeing it, it doesn't stop errors occuring :).

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

View this thread on the Works forum...