[AccessD] Classes not recognized in mda

In step 4 that John outlined you do *not* paste the complete text of the
class code into the new, empty class module. Rather, you open the new class
module, and then from the File menu select 'Insert File' (or is it the
Insert menu - I can't tell right now as my copy of Access 2002 is doing its
usual thing right now --- Taking several minutes to save a few lines of
code, which will result in me having YET ANOTHER CORRUPT FILE THAT I NEED TO
RESTORE FROM BACKUP!!!!! Every dammed day this happens to me grrrrr!!!!) ---

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim
Sent: Wednesday, June 22, 2005 11:59 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Classes not recognized in mda


The new class doesn't like the Attribute keyword. Am I missing a reference
perhaps? Jim Hale

-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com]
Sent: Wednesday, June 22, 2005 10:22 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Classes not recognized in mda


Yes, you have to:

1) Export the classes to text files
2) Edit the text file to set two properties
3) Delete the original class in your lib.
4) Insert a new class
5) Insert the file into that class.  
6) Save the new class.

The top of an exported class will look something like:

VERSION 1.0 CLASS
BEGIN
  MultiUse = -1  'True
END
Attribute VB_Name = "clsSysVars"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = False
Attribute VB_Exposed = False
Option Compare Database
Option Explicit

You need to change it to look like:

Attribute VB_Name = "clsSysVars"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = True
Attribute VB_PredeclaredId = False
Attribute VB_Exposed = True

Notice all the stuff I got rid of, and also notice that I changed two
properties from False to True.

That should take care of you.

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 11: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

***********************************************************************
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.