|
 |
access thread: 2000 upgrade issue
Message #1 by DHolloway1@a... on Wed, 28 Mar 2001 20:46:22
|
|
I have been working on a database taht I upgraded from 97 to 2000.
When It converted ok and runs as normal but when I tried to go into a
form code module it wouldn't open and I get some error about a DLL file
missing.
Has anyone ever heard of this one where you can't even open the code
window of a form?
HELP!!!!
Dennis L. Holloway
Message #2 by "Pardee, Roy E" <roy.e.pardee@l...> on Wed, 28 Mar 2001 12:56:29 -0800
|
|
Sounds like a problem w/your 2000 install. I'd try searching the knowlege
base for articles referring to the dll that Access is complaining about
(http://support.microsoft.com/servicedesks/msdn/) and if that didn't shed
light, re-install Access 2000. Have you tried opening it up on a different
machine that had A2k installed?
HTH,
-Roy
-----Original Message-----
From: DHolloway1@a... [mailto:DHolloway1@a...]
Sent: Wednesday, March 28, 2001 12:45 PM
To: Access
Subject: [access] 2000 upgrade issue
I have been working on a database taht I upgraded from 97 to 2000.
When It converted ok and runs as normal but when I tried to go into a
form code module it wouldn't open and I get some error about a DLL file
missing.
Has anyone ever heard of this one where you can't even open the code
window of a form?
HELP!!!!
Dennis L. Holloway
Message #3 by "Brian Paniccia" <bpanicci@n...> on Thu, 29 Mar 2001 14:52:01 -0500
|
|
DHolloway,
I Would re-run the option that produced the error and log the name of the
dll that would not load.
In some cases I've seen Access and other software skip a .dll that was
critical. A second step would be to
check the dll's loaded from Access under Help - System Info - Loaded Modules
and Running Tasks.
Cross check the .dll in the error message against these, and additionally
check your drive for the missing .dll
This helps zero in on the file in question and is a 1000% more of an
informed base to continue with .
Check these then post back an e-mail with the results and we can do a couple
of things, get a copy of the dll
to you if it's not already there, and re-register the dll and see if that
doesn't fix the problem. Another check you may want to make is find out what
VB references you have installed. Under Tools -References from a VB design
mode window, within Access.
This option may point to a DAO, or prev compatibility reference used within
your 97 application that is not automatically available in the 2000 install,
if so it's a quick selection from the list of references to fix.
Note: You have to go into a module or form design mode and invoke the edit
window (VB) to pick the Tools References
I would then list the ones you have checked and post that information back
as well, and then I'm certain we can fix your problem.
BRIAN
----- Original Message -----
From: <DHolloway1@a...>
To: "Access" <access@p...>
Sent: Wednesday, March 28, 2001 8:46 PM
Subject: [access] 2000 upgrade issue
> I have been working on a database taht I upgraded from 97 to 2000.
> When It converted ok and runs as normal but when I tried to go into a
> form code module it wouldn't open and I get some error about a DLL file
> missing.
>
> Has anyone ever heard of this one where you can't even open the code
> window of a form?
>
> HELP!!!!
>
>
> Dennis L. Holloway
>
Message #4 by DHolloway1@a... on Fri, 30 Mar 2001 10:32:47
|
|
Brian,
The error comes up in a normal msgbox. Title is "Visual Basic". There
is no error number and the errordesc is "error in loading DLL", nothing
else. It doesn't say which DLL.
I have taken a look at the references and it shows that I am missing
Microsoft Common Dialog 6.0 (SP3) (IE "CMDLG32.OCX"). I have confirmed
that the file is there and re-registered it. Registered OK.
Still shows that it is missing under References, but even so I have done
that one before and it has never caused me to not be able to get into the
code window of a form before.
The interesting thing is that I can add a normal code module but even
when I add a new form, it will not let me goto the form code module.
At a loss......and frustrated!
Dennis
> DHolloway,
> I would re-run the option that produced the error and log the name of the
> dll that would not load.
> In some cases I've seen Access and other software skip a .dll that was
> critical. A second step would be to
> check the dll's loaded from Access under Help - System Info - Loaded
Modules
> and Running Tasks.
>
> Cross check the .dll in the error message against these, and additionally
> check your drive for the missing .dll
>
> This helps zero in on the file in question and is a 1000% more of an
> informed base to continue with .
>
> Check these then post back an e-mail with the results and we can do a
couple
> of things, get a copy of the dll
> to you if it's not already there, and re-register the dll and see if that
> doesn't fix the problem. Another check you may want to make is find out
what
> VB references you have installed. Under Tools -References from a VB
design
> mode window, within Access.
>
> This option may point to a DAO, or prev compatibility reference used
within
> your 97 application that is not automatically available in the 2000
install,
> if so it's a quick selection from the list of references to fix.
>
> Note: You have to go into a module or form design mode and invoke the
edit
> window (VB) to pick the Tools References
>
> I would then list the ones you have checked and post that information
back
> as well, and then I'm certain we can fix your problem.
>
> BRIAN
>
>
> ----- Original Message -----
> From: <DHolloway1@a...>
> To: "Access" <access@p...>
> Sent: Wednesday, March 28, 2001 8:46 PM
> Subject: [access] 2000 upgrade issue
>
>
> > I have been working on a database taht I upgraded from 97 to 2000.
> > When It converted ok and runs as normal but when I tried to go into a
> > form code module it wouldn't open and I get some error about a DLL file
> > missing.
> >
> > Has anyone ever heard of this one where you can't even open the code
> > window of a form?
> >
> > HELP!!!!
> >
> >
> > Dennis L. Holloway
> >
>
Message #5 by "Pardee, Roy E" <roy.e.pardee@l...> on Fri, 30 Mar 2001 07:11:01 -0800
|
|
I can think of two other things to try:
First, create a new, empty mdb file & import all the objects from the
problematic one into it. Watch closely at the import process--if it dies at
a specific form or module, that form or module may be corrupt.
Second, decompile the database (do this on a copy of the file!).
Instructions & caveats for doing so may be found at
http://www.mvps.org/access/bugs/bugs0008.htm
HTH,
-Roy
-----Original Message-----
From: DHolloway1@a... [mailto:DHolloway1@a...]
Sent: Friday, March 30, 2001 2:32 AM
To: Access
Subject: [access] Re: 2000 upgrade issue
Brian,
The error comes up in a normal msgbox. Title is "Visual Basic". There
is no error number and the errordesc is "error in loading DLL", nothing
else. It doesn't say which DLL.
I have taken a look at the references and it shows that I am missing
Microsoft Common Dialog 6.0 (SP3) (IE "CMDLG32.OCX"). I have confirmed
that the file is there and re-registered it. Registered OK.
Still shows that it is missing under References, but even so I have done
that one before and it has never caused me to not be able to get into the
code window of a form before.
The interesting thing is that I can add a normal code module but even
when I add a new form, it will not let me goto the form code module.
At a loss......and frustrated!
Dennis
> DHolloway,
> I would re-run the option that produced the error and log the name of the
> dll that would not load.
> In some cases I've seen Access and other software skip a .dll that was
> critical. A second step would be to
> check the dll's loaded from Access under Help - System Info - Loaded
Modules
> and Running Tasks.
>
> Cross check the .dll in the error message against these, and additionally
> check your drive for the missing .dll
>
> This helps zero in on the file in question and is a 1000% more of an
> informed base to continue with .
>
> Check these then post back an e-mail with the results and we can do a
couple
> of things, get a copy of the dll
> to you if it's not already there, and re-register the dll and see if that
> doesn't fix the problem. Another check you may want to make is find out
what
> VB references you have installed. Under Tools -References from a VB
design
> mode window, within Access.
>
> This option may point to a DAO, or prev compatibility reference used
within
> your 97 application that is not automatically available in the 2000
install,
> if so it's a quick selection from the list of references to fix.
>
> Note: You have to go into a module or form design mode and invoke the
edit
> window (VB) to pick the Tools References
>
> I would then list the ones you have checked and post that information
back
> as well, and then I'm certain we can fix your problem.
>
> BRIAN
>
>
> ----- Original Message -----
> From: <DHolloway1@a...>
> To: "Access" <access@p...>
> Sent: Wednesday, March 28, 2001 8:46 PM
> Subject: [access] 2000 upgrade issue
>
>
> > I have been working on a database taht I upgraded from 97 to 2000.
> > When It converted ok and runs as normal but when I tried to go into a
> > form code module it wouldn't open and I get some error about a DLL file
> > missing.
> >
> > Has anyone ever heard of this one where you can't even open the code
> > window of a form?
> >
> > HELP!!!!
> >
> >
> > Dennis L. Holloway
> >
Message #6 by "Brian Paniccia" <bpanicci@n...> on Fri, 30 Mar 2001 13:53:48 -0500
|
|
Dennis,
1) Do a list for me of the checked references that are loaded within the mdb
2) Also do a list of the sytem info loaded drivers, and dll's you can export
the detail file list
Put these in an attachement for a look.
3) Have you patched and revised your operating system and office to the
latest builds,
When in doubt update
Remember Office 2000 from the CD is allready outdated in terms of the
latest build
4) One other qeustion do you have a VB install sperate from Office 2000 ?
5) What are the versions of Windows, VB if you have it, and are you running
other versions on the same machine
After this there are a couple of other things we could try
----- Original Message -----
From: <DHolloway1@a...>
To: "Access" <access@p...>
Sent: Friday, March 30, 2001 10:32 AM
Subject: [access] Re: 2000 upgrade issue
> Brian,
>
> The error comes up in a normal msgbox. Title is "Visual Basic". There
> is no error number and the errordesc is "error in loading DLL", nothing
> else. It doesn't say which DLL.
>
> I have taken a look at the references and it shows that I am missing
> Microsoft Common Dialog 6.0 (SP3) (IE "CMDLG32.OCX"). I have confirmed
> that the file is there and re-registered it. Registered OK.
> Still shows that it is missing under References, but even so I have done
> that one before and it has never caused me to not be able to get into the
> code window of a form before.
>
> The interesting thing is that I can add a normal code module but even
> when I add a new form, it will not let me goto the form code module.
>
> At a loss......and frustrated!
>
> Dennis
>
|
|
|
View Cart
