Re: expose class modules of a referenced mde
- From: "Jamey Shuemaker" <cantankeris@xxxxxxxxx>
- Date: 18 Apr 2006 17:29:15 -0700
Yes, tried both methods in fact. Here's the latest.
Exported the class to a .cls file and altered the settings as above.
Imported it using the import option. That doesn't work because it
doesn't retain the Creatable attribute.
Inserted it from the .cls file. That doesn't work because it doesn't
retain the Creatable attribute.
Changed the .cls file to a .txt file, changed the attributes as above.
Inserted it from the .txt file. That works and properly exposes the
class to a referencing database IF I leave the thing an .mdb.
Access won't let me save it as an .mde for reasons unknown to me. Since
I can't reference an .mdb from an .mde (which is what the final app
will wind up being) it's not very useful to me in its current form. Not
sure what it is about making it an .mde that Access doesn't like, but
for now I'll just leave the standard modules in the reference file and
import the class objects as needed into the app.
If you have any ideas on the .mde deal, let me know.
Thanks for the help up to this point....Jamey
- Prev by Date: Re: Transfertxt problem; difference A97 and A2k
- Next by Date: Designing Access apps for differing resolutions
- Previous by thread: Re: expose class modules of a referenced mde
- Next by thread: Re: expose class modules of a referenced mde