Our app does not have any tables defined for the application;

this is to allow different subdirectories based on conditions.

problem: sysvolumes and systables are not in sync after the

detach_table; and detach_volume. Scott, great guy, emailed the

syncdb procedure but because our tables are not defined in the

dbt all tables are unattached. Are there any options; other than

reattching everything.

in AREV it is no problem, but openinsight doesn't appear to like

it. Thank you for your help.

Hi Debbie,

I cannot tell from your post when the SYSVOLUMES and SYSTABLES become desynchronized, or if your issue is the one that SYNCDB is designed to address.

Our app does not have any tables defined for the application; this is to allow different subdirectories based on conditions.

In other words, only the system tables are attached when the application starts. At that point, is the database synchronized? (Does SYNCDB report anything?)

problem: sysvolumes and systables are not in sync after the detach_table; and detach_volume.

Do you mean after you attach your application tables then detach them? If they are not in sync afterwords, I would guess that they are not in synch before. The only way I know of to get un-synchronized is to have the .dbt contain unsynchronized information. Could you run SYNCDB after each step (logging in, attaching the data tables, detaching the data tables, attaching other data tables) to see when it gets out of sync?

Scott, great guy

No kidding. He's a bright little guy, isn't he? We just hope that no one finds out that he's too young to work here.

If you are not able to resolve this on site, send the sysprog.dbt and the .dbt for your application to Scott. He should be able to verify here whether or not there is a problem with the .dbt files you are using.

Cameron Purdy

Revelation Software

View this thread on the forum...