[AccessD] Classes not recognized in mda

It's a little tricky using classes in a code library because you have to
give them a public interface before they can be used elsewhere.  I don't
have an example on this machine, so I'm working from memory here, but as
I recall, I dimmed a public object variable as a new instance of the
class I wanted to expose.  That allowed the app linked to the library to
grab the public instance of the class and use its methods and
properties.    

Charlotte Foust


-----Original Message-----
From: Hale, Jim [mailto:Jim.Hale at fleetpride.com] 
Sent: Wednesday, June 22, 2005 8:01 AM
To: 'Accessd (E-mail)
Subject: [AccessD] Classes not recognized in mda


I have moved some classes and modules out of the front end into a code
library. I set the same references in the code library as in the front
end. In the front end I set a reference to the code library. The FE
recognizes the functions in the library modules fine, no problems but
doesn't recognize the classes (i.e. I get an error in the FE when I try
to instantiate the moved classes). The code ran fine when the classes
resided in the front end. I am obviously doing something simple wrong.
Any suggestions? TIA Jim Hale

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other
use of or taking action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you have
received this email in error please contact the sender and delete the
material from any computer. As a recipient of this email, you are
responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.