>Thanks,
>
>I was using the more novice way to create views by using the gadgets in the DBC container, then creating the remote view as a way to get the free table into the DBC without making it unavailable to SBT. Your code method should be better. Also, I did use gendbc to get similar code from my views.
>
>As for multi-companies, you can easily make the approach work with multiple companies by setting up the SQL statement as a string with substitution, and then substituting other definitions as needed. Here's an example.

Get the EView app here on the UT fiels section. It's not as good as Stonefield, but its free!

What I do, is start the view in the dbc. Save it as the name I want. I then open up eView and edit the view. I then create source code for it and save that to the prgs directory.

Now I can take a base view and change what I need, add params, etc.

This is a lot harder where you could do all this in Stonefield, but here at work we are cheap after our biggest customer declared bankruptsy.

I am going to look at your code. It's very scarry because all that a. and b. reminds me of the dreaded SBT look and feel. {just kidding}