Thanks. I've tried that and it does not work (no errors, no indices built).

I might be crazy, but I don't see your example.

I hate to be a bother, and I agree, sounds like 2 classes would be more appropriate, but I've yet to create a View in this system (I'm fluent in MySQL, FYI), and frankly, I don't like views (been burned on performance issues too many times). However, any way you could show me the basics of both (2 classes with a view and 1 class), just so I understand better how this works. I know that's a lot to ask, but I've read a lot of docs, and some aspects I still do not understand.

If not, no big deal. I probably won't use the view because we are mirroring these "tables" into MySQL anyway and prefer to keep that part simple - 1 ODBC class = 1 MySQL table.

Also, and don't hit me, but we are on a very old version of Cache (and no way to fix that, blame our vendor).

Cache for Windows (x86-64) 2013.1 (Build 446) Tue Apr 23 2013 12:10:38 EDT

Well, that was actually what I was planning on doing if there was no other way, but I was hoping I was wrong.

I can't modify the Globals structure - we are using a 3rd Party application and the only thing we can do is add and modify the classes used for ODBC.

Thanks for the quick response.

Thanks, and that is helpful, but I already read those articles and either they did not answer my question or I don't understand the problem well enough.