John W. Colby
jwcolby at colbyconsulting.com
Wed Jun 22 16:56:41 CDT 2005
Forms can be placed in libraries. Unbound forms (non data forms) are easy, bound forms are trickier. Referencing them requires calling a function that opens the form. The issue with bound forms is that the table name or query for a form is assumed to be in the database container that the form resides in. The easiest way around that is to use a SQL statement that uses an "in databasename" clause. Typically you would have the form open not bound to a recordsource, then have it set it's recordsource to the passed in sql statement. Not pretty but it can be made to work. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim Sent: Wednesday, June 22, 2005 5:50 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Classes not recognized in mda Can forms be placed in libraries? If so how are they referenced? Jim Hale -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Wednesday, June 22, 2005 10:25 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Classes not recognized in mda Hmm... This is the other way of doing it. What Charlotte is saying is that INSIDE of the library you can set a function that dims a new instance and returns a pointer to the class. The problem with doing this is that you can't use intellisense to see the properties of the class etc. whereas using the method I described, your classes become just another object and you can use it just as you would any other object. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, June 22, 2005 11:15 AM To: Access Developers discussion and problem solving Subject: RE: [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. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com *********************************************************************** 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.