stormin_norm
Registered User.
- Local time
- Today, 05:04
- Joined
- Apr 23, 2003
- Messages
- 213
This one will stump you! I don't think there is a way to fix this problem! Help!
I have a database and made some changes to queries, forms, reports, and vb public module. The easiest way for me to move it into production is to simply rename the old objects and import the new ones. (Yes I know I must convince my client to use FE/BE).
The problem is I imported the VB public module holding 10 routines. I should have simply deleted it right away...but did not. I realized my slip when I went to test my forms and received an 'ambiguous name' error since there were now two modules holding public subroutines with the same name.
So I simply went back to the access list of objects and deleted the public module. I may have hit compile before the delete.
The delete did not get rid of the object class. When I went into the VBA object browser I see the two modules!
Something like:
class: global
Public Function GetGroupName() As String
Member of Prospect.Prospect Form
Public Function GetGroupName() As String
Member of Prospect.Prospect Form SAVE
If I click on the "Prospect Form SAVE" to view the definition, access crashes with an error because the module "Prospect Form SAVE" does not exist in 'text' format for editing, just a compiled format.
SO what can I do???????
Is there a way to create the class using vb code? Then delete it? OR can I get to the compiled vb class via vb code??
or...
Rename all my global functions to new names & modify every call to them?
or the other option is to completely import EVERY object into a new database thus eliminating the "ghost" class object "Prospect Form SAVE"
I have a database and made some changes to queries, forms, reports, and vb public module. The easiest way for me to move it into production is to simply rename the old objects and import the new ones. (Yes I know I must convince my client to use FE/BE).
The problem is I imported the VB public module holding 10 routines. I should have simply deleted it right away...but did not. I realized my slip when I went to test my forms and received an 'ambiguous name' error since there were now two modules holding public subroutines with the same name.
So I simply went back to the access list of objects and deleted the public module. I may have hit compile before the delete.
The delete did not get rid of the object class. When I went into the VBA object browser I see the two modules!
Something like:
class: global
Public Function GetGroupName() As String
Member of Prospect.Prospect Form
Public Function GetGroupName() As String
Member of Prospect.Prospect Form SAVE
If I click on the "Prospect Form SAVE" to view the definition, access crashes with an error because the module "Prospect Form SAVE" does not exist in 'text' format for editing, just a compiled format.
SO what can I do???????
Is there a way to create the class using vb code? Then delete it? OR can I get to the compiled vb class via vb code??
or...
Rename all my global functions to new names & modify every call to them?
or the other option is to completely import EVERY object into a new database thus eliminating the "ghost" class object "Prospect Form SAVE"
Last edited: