It appears that when the generated queries access values from a sequence, it does not prepend the sequence name with the schema name..is this by design? Do I need to have the DBA create public synonyms for each sequence?

I've never heard of any customer using oracle this was a problem, but now you mention it, it indeed doesn't include the schema in front of the sequence name. I'll add this to 1.0.2004.2 DQE. I've to do some testing though, something tells me it didn't work with the schema name in front of it.

Ok, thanks. Let me know if you post a fix, otherwise I'll just have the DBA create synonyms for all the sequences.

It's added to the next build of 1.0.2004.2 beta.

It required some conversion code to be added, as it otherwise didn't go well when refreshes were performed.

(edit). You only run into probs at the moment by not being able to use the sequences is when you use a different account to log in as the schema owner. If you use for the time being the schema-owner account, the code works as planned.

Great, thanks Frans! I'm just using public synonyms for the sequences in the meantime, so that the schema name doesn't need to be prepended to the sequence name.