>Harry,
>
>< looks like what I need. Where can I find an example of how this is done in practice and how each PDS can then access the tables opened by the global class? >
>
>I think what Bob means is the application-level class will handle all table access for you, when your PDS form calls the application-level class's methods.
>
>For example, your form calls oApp.oUser.CheckSecurity("yourFormName") to see if the currently logged-in user has access rights to a restricted portion of the form. The CheckSecurity method of oUser, which is attached to oApp, will access the security table, so your form does not need to change datasession, etc.
>
>Several of the commercial frameworks probably use this style of application-level objects that are callable from anywhere in the app. Perhaps you can do a thread search on application object and find some examples, or visit the sites of framework vendors for examples.

>The point is that if you can wrap table access in method calls at the app level, you simplify the data-session switching needed for direct access to tables outside the PDS.
>

I think I now understand the principles so I'm trying to put them into practice.

I went and had a look at the Tastrade applicatiion class and tried to create a simple version of my own. Can't seem to get to first base. I've created the custom class and added a couple of methods and properties to it for trial purposes, saved it as part of my main visual class library and tried to run it from my startup program. It falls over straight away telling me it can't find the class definition. Thats got me stumped at square one as its right where all my other classes are!

What do I need to do to get it to see the new class?

Harry