|
 |
access thread: Problems creating an *.mde file
Message #1 by "Kenny Alligood" <kennyalligood@h...> on Thu, 12 Dec 2002 01:51:15
|
|
I seem to have a problem that I can't figure out. It relates to my trying
to create an *.mde file out of an *.mdb file. I continue to get the
following error message with no indication of what the error is:
"Microsoft Access was unable to create the MDE database"
This is my working database that I edit - update - whatever and always
change to an *.mde for the production run. I have compiled all my code and
everything appears to function as usual. Any assistance or ideas would be
greatly appreciated.
Kenny
Message #2 by "John Ruff" <papparuff@a...> on Wed, 11 Dec 2002 17:50:42 -0800
|
|
This normally means that there is an error in your code somewhere. Open
any module and compile the db.
John V. Ruff - The Eternal Optimist :-)
Always Looking For Contract Opportunities
www.noclassroom.com
Live software training
Right over the Internet
Home: xxx.xxx.xxxx
Cell: 253.307/2947
9306 Farwest Dr SW
Lakewood, WA 98498
"Commit to the Lord whatever you do,
and your plans will succeed." Proverbs 16:3
-----Original Message-----
From: Kenny Alligood [mailto:kennyalligood@h...]
Sent: Thursday, December 12, 2002 1:51 AM
To: Access
Subject: [access] Problems creating an *.mde file
I seem to have a problem that I can't figure out. It relates to my
trying
to create an *.mde file out of an *.mdb file. I continue to get the
following error message with no indication of what the error is:
"Microsoft Access was unable to create the MDE database"
This is my working database that I edit - update - whatever and always
change to an *.mde for the production run. I have compiled all my code
and
everything appears to function as usual. Any assistance or ideas would
be
greatly appreciated.
Kenny
Message #3 by "Haslett, Andrew" <andrew.haslett@i...> on Thu, 12 Dec 2002 12:28:15 +1030
|
|
http://support.microsoft.com/default.aspx?scid=KB;en-us;q283788
http://support.microsoft.com/default.aspx?scid=KB;en-us;q202304
-----Original Message-----
From: Kenny Alligood [mailto:kennyalligood@h...]
Sent: Thursday, 12 December 2002 12:21 PM
To: Access
Subject: [access] Problems creating an *.mde file
I seem to have a problem that I can't figure out. It relates to my trying
to create an *.mde file out of an *.mdb file. I continue to get the
following error message with no indication of what the error is:
"Microsoft Access was unable to create the MDE database"
This is my working database that I edit - update - whatever and always
change to an *.mde for the production run. I have compiled all my code and
everything appears to function as usual. Any assistance or ideas would be
greatly appreciated.
Kenny
IMPORTANT - PLEASE READ ********************
This email and any files transmitted with it are confidential and may
contain information protected by law from disclosure.
If you have received this message in error, please notify the sender
immediately and delete this email from your system.
No warranty is given that this email or files, if attached to this
email, are free from computer viruses or other defects. They
are provided on the basis the user assumes all responsibility for
loss, damage or consequence resulting directly or indirectly from
their use, whether caused by the negligence of the sender or not.
Message #4 by John Fejsa <John.Fejsa@h...> on Thu, 12 Dec 2002 15:22:51 +1100
|
|
make sure that you compile the code in your database and repair any
errors before converting to mde.
1) Open any module and Click Tools, Compile and Save All Modules (in
Access 97) or Tools, Compile in Access XP
2) Convert to MDE file
____________________________________________________
John Fejsa
Systems Analyst/Computer Programmer
Hunter Centre for Health Advancement
Locked Bag 10, WALLSEND NSW 2287
Phone: (02) 4924 6336 Fax: (02) 4924 6209
www.hcha.org.au
____________________________________________________
The doors we open and close each day decide the lives we live
____________________________________________________
CONFIDENTIALITY & PRIVILEGE NOTICE
>>> kennyalligood@h... 12/12/2002 12:51:15 >>>
I seem to have a problem that I can't figure out. It relates to my
trying
to create an *.mde file out of an *.mdb file. I continue to get the
following error message with no indication of what the error is:
"Microsoft Access was unable to create the MDE database"
This is my working database that I edit - update - whatever and always
change to an *.mde for the production run. I have compiled all my code
and
everything appears to function as usual. Any assistance or ideas would
be
greatly appreciated.
Kenny
This message is intended for the addressee named
and may contain confidential information.
If you are not the intended recipient, please
delete it and notify the sender.
Views expressed in this message are those of the
individual sender, and are not necessarily the
views of Hunter Health.
Message #5 by "Kenny Alligood" <kennyalligood@h...> on Thu, 12 Dec 2002 18:40:58
|
|
Thanx for the reply. When I tried to compile the code I get the following
error:
"Compile Error: Can't find project or library"
When I click OK on the dialog it opens up the references dialog box which
leads me to believe that I am missing a reference all of the sudden. The
only problem is that I have all the references listed that I previously
had and haven't done anything to alter the DB where it would require a new
reference. The next problem is I would sure like to know of a place that
explains what the references are for and what they do. Any ideas....?
Kenny
Message #6 by "Kenny Alligood" <kennyalligood@h...> on Thu, 12 Dec 2002 20:59:52
|
|
Thanx for the suggestion. I did that (with all my forms, modules, and
reports) and everything now complies without any complications. However, I
am still unable to create the MDE. Would you have any other suggestions??
Kenny
Message #7 by "Bob Bedell" <bobbedell15@m...> on Fri, 13 Dec 2002 19:59:38
|
|
>The next problem is I would sure like to know of a place that
>explains what the references are for and what they do. Any ideas....?
Hi Kenny,
References are objects, with properties (but no methods), just like any
other object you use in your apps. When you check a reference in the
References Dialog, you are really telling Access to instantiate a
Reference Object and add it to the Application Object?s References
Collection. You can declare a Reference Object in code with:
Dim ref As Reference
Access uses Reference Objects to point to Component Object Model (COM)
dynamic link libraries (.dll), object libraries (.olb), or type libraries
(.tlb) installed on your computer with an entry in the Registry. The
References Dialog displays these installed COM libraries. A Reference
Object?s FullPath property, for example, contains the path and file name
of the COM library it points to. A Reference Object?s IsBroken property
indicates whether or not the Reference Object points to a valid reference
in the Windows Registry. The COM libraries encapsulate and expose (make
available) objects (or, more correctly, classes) to Access for use in code
modules. A Class is simply a generic template from which an instance of a
particular type of object is created (or instantiated) at run-time.
You can view the contents of these libraries in the Object Browser (press
F2 in the Visual Basic Editor). The combo box at the top of the Object
Browser lets you select any of the COM libraries currently referenced by
your application. The 'Classes' pane of the Object Browser lists all the
currently referenced Classes contained in those libraries that can be used
to instantiate objects in your code. The 'Members' pane of the Object
Browser lists all the properties (including event properties) and methods
available for each of the available Classes. You'll also see lists of all
the constants available as argument values.
You can read more about the Reference Object and the Refereces Collection
in the Help File.
The list below (I just stumbled upon this) lists the major object library
names and their file names and paths of the major Office application
libraries (compiled by Helen Feddema). The Object Library names are what
you see in the Refernces Dialog.
Office 97
Access 97:
Object Library Name: Microsoft Access 8.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msacc8.olb
Excel 97
Object Library Name: Microsoft Excel 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\excel8.olb
Outlook 98
Object Library Name: Outlook 98 Type Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msoutl85.olb
Word 97
Object Library Name: Microsoft Word 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msword8.olb
Office 2000
Access 2000
Object Library Name: Microsoft Access 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msacc9.olb
Excel 2000
Object Library Name: Microsoft Excel 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\excel9.olb
Outlook 2000
Object Library Name: Microsoft Outlook 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msoutl9.olb
Word 2000
Object Library Name: Microsoft Word 9.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office\msword9.olb
DAO 3.51
Object Library Name: Microsoft DAO 3.51 Object Library
File Name and Path: C:\Program Files\Common Files\Microsoft
Shared\DAO\dao350.dll
ADO 2.1
Object Library Name: Microsoft ActiveX Data Objects 2.1 Library
File Name and Path: C:\Program Files\Common Files\system\ado\msado21.tlb
Office XP
Access 2002
Object Library Name: Microsoft Access 10.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office10\msacc.olb
Excel 2002
Object Library Name: Microsoft Excel 10.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office10\excel.exe
Outlook 2002
Object Library Name: Microsoft Outlook 10.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office10\msoutl.olb
Word 2002
Object Library Name: Microsoft Word 10.0 Object Library
File Name and Path: C:\Program Files\Microsoft Office\Office10\msword.olb
DAO 3.6
Object Library Name: Microsoft DAO 3.6 Object Library
File Name and Path: C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll
ADO 2.5
Object Library Name: Microsoft ActiveX Data Objects 2.5 Library File
Name and Path: C:\Program Files\Common Files\system\ado\msado25.tlb
Message #8 by "Bob Bedell" <bobbedell15@m...> on Fri, 13 Dec 2002 20:51:39
|
|
Or did you already know everthing I just blabbered about, and instead want
to know what kinds of functionality the various libraries contain IN
PARTICULAR, and not what the various libraries are in general?
The possibility of this second reading of your question just occurred to
me, in which case:
a) I apologize for running on at length about something you already
understand (though a good 75% of the effort I expend here is really
about teaching myself these topics anyway :), and
b) I'd like to know the answer to version two of your question, too.
Thanks,
Bob
> >The next problem is I would sure like to know of a place that
>> explains what the references are for and what they do. Any ideas....?
> Hi Kenny,
> References are objects, with properties (but no methods), just like any
o> ther object you use in your apps. When you check a reference in the
R> eferences Dialog, you are really telling Access to instantiate a
R> eference Object and add it to the Application Object?s References
C> ollection. You can declare a Reference Object in code with:
> Dim ref As Reference
> Access uses Reference Objects to point to Component Object Model (COM)
d> ynamic link libraries (.dll), object libraries (.olb), or type
libraries
(> .tlb) installed on your computer with an entry in the Registry. The
R> eferences Dialog displays these installed COM libraries. A Reference
O> bject?s FullPath property, for example, contains the path and file name
o> f the COM library it points to. A Reference Object?s IsBroken property
i> ndicates whether or not the Reference Object points to a valid
reference
i> n the Windows Registry. The COM libraries encapsulate and expose (make
a> vailable) objects (or, more correctly, classes) to Access for use in
code
m> odules. A Class is simply a generic template from which an instance of
a
p> articular type of object is created (or instantiated) at run-time.
>
Y> ou can view the contents of these libraries in the Object Browser
(press
F> 2 in the Visual Basic Editor). The combo box at the top of the Object
B> rowser lets you select any of the COM libraries currently referenced by
y> our application. The 'Classes' pane of the Object Browser lists all the
c> urrently referenced Classes contained in those libraries that can be
used
t> o instantiate objects in your code. The 'Members' pane of the Object
B> rowser lists all the properties (including event properties) and
methods
a> vailable for each of the available Classes. You'll also see lists of
all
t> he constants available as argument values.
> You can read more about the Reference Object and the Refereces
Collection
i> n the Help File.
> The list below (I just stumbled upon this) lists the major object
library
n> ames and their file names and paths of the major Office application
l> ibraries (compiled by Helen Feddema). The Object Library names are what
y> ou see in the Refernces Dialog.
> Office 97
> Access 97:
O> bject Library Name: Microsoft Access 8.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msacc8.olb
> Excel 97
O> bject Library Name: Microsoft Excel 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\excel8.olb
> Outlook 98
O> bject Library Name: Outlook 98 Type Library
F> ile Name and Path: C:\Program Files\Microsoft
Office\Office\msoutl85.olb
> Word 97
O> bject Library Name: Microsoft Word 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msword8.olb
> Office 2000
> Access 2000
O> bject Library Name: Microsoft Access 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msacc9.olb
> Excel 2000
O> bject Library Name: Microsoft Excel 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\excel9.olb
> Outlook 2000
O> bject Library Name: Microsoft Outlook 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msoutl9.olb
>
W> ord 2000
O> bject Library Name: Microsoft Word 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msword9.olb
> DAO 3.51
O> bject Library Name: Microsoft DAO 3.51 Object Library
F> ile Name and Path: C:\Program Files\Common Files\Microsoft
> Shared\DAO\dao350.dll
> ADO 2.1
O> bject Library Name: Microsoft ActiveX Data Objects 2.1 Library
F> ile Name and Path: C:\Program Files\Common Files\system\ado\msado21.tlb
> Office XP
> Access 2002
O> bject Library Name: Microsoft Access 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10\msacc.olb
> Excel 2002
O> bject Library Name: Microsoft Excel 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10\excel.exe
> Outlook 2002
O> bject Library Name: Microsoft Outlook 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10
\msoutl.olb
> Word 2002
O> bject Library Name: Microsoft Word 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10
\msword.olb
> DAO 3.6
O> bject Library Name: Microsoft DAO 3.6 Object Library
F> ile Name and Path: C:\Program Files\Common Files\Microsoft
> Shared\DAO\dao360.dll
A> DO 2.5
O> bject Library Name: Microsoft ActiveX Data Objects 2.5 Library File
N> ame and Path: C:\Program Files\Common Files\system\ado\msado25.tlb
>
Message #9 by "Kenny Alligood" <kennyalligood@h...> on Sat, 14 Dec 2002 15:10:56 -0500
|
|
Thanx Bob. I did want to know the functionality (particularly what each library accomplishes) and you
may have answered that by directing me to the Object Browser. Regardless, what you call blabbering had some really good information
included that I think will help me and others. Thanx and if I get an answer I will surely let you know.
Kenny
----- Original Message -----
From: Bob Bedell
Sent: Friday, December 13, 2002 3:38 PM
To: Access
Subject: [access] RE: Problems creating an *.mde file
Or did you already know everthing I just blabbered about, and instead want
to know what kinds of functionality the various libraries contain IN
PARTICULAR, and not what the various libraries are in general?
The possibility of this second reading of your question just occurred to
me, in which case:
a) I apologize for running on at length about something you already
understand (though a good 75% of the effort I expend here is really
about teaching myself these topics anyway :), and
b) I'd like to know the answer to version two of your question, too.
Thanks,
Bob
> >The next problem is I would sure like to know of a place that
>> explains what the references are for and what they do. Any ideas....?
> Hi Kenny,
> References are objects, with properties (but no methods), just like any
o> ther object you use in your apps. When you check a reference in the
R> eferences Dialog, you are really telling Access to instantiate a
R> eference Object and add it to the Application Objectâ??s References
C> ollection. You can declare a Reference Object in code with:
> Dim ref As Reference
> Access uses Reference Objects to point to Component Object Model (COM)
d> ynamic link libraries (.dll), object libraries (.olb), or type
libraries
(> .tlb) installed on your computer with an entry in the Registry. The
R> eferences Dialog displays these installed COM libraries. A Reference
O> bjectâ??s FullPath property, for example, contains the path and file name
o> f the COM library it points to. A Reference Objectâ??s IsBroken property
i> ndicates whether or not the Reference Object points to a valid
reference
i> n the Windows Registry. The COM libraries encapsulate and expose (make
a> vailable) objects (or, more correctly, classes) to Access for use in
code
m> odules. A Class is simply a generic template from which an instance of
a
p> articular type of object is created (or instantiated) at run-time.
>
Y> ou can view the contents of these libraries in the Object Browser
(press
F> 2 in the Visual Basic Editor). The combo box at the top of the Object
B> rowser lets you select any of the COM libraries currently referenced by
y> our application. The 'Classes' pane of the Object Browser lists all the
c> urrently referenced Classes contained in those libraries that can be
used
t> o instantiate objects in your code. The 'Members' pane of the Object
B> rowser lists all the properties (including event properties) and
methods
a> vailable for each of the available Classes. You'll also see lists of
all
t> he constants available as argument values.
> You can read more about the Reference Object and the Refereces
Collection
i> n the Help File.
> The list below (I just stumbled upon this) lists the major object
library
n> ames and their file names and paths of the major Office application
l> ibraries (compiled by Helen Feddema). The Object Library names are what
y> ou see in the Refernces Dialog.
> Office 97
> Access 97:
O> bject Library Name: Microsoft Access 8.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msacc8.olb
> Excel 97
O> bject Library Name: Microsoft Excel 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\excel8.olb
> Outlook 98
O> bject Library Name: Outlook 98 Type Library
F> ile Name and Path: C:\Program Files\Microsoft
Office\Office\msoutl85.olb
> Word 97
O> bject Library Name: Microsoft Word 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msword8.olb
> Office 2000
> Access 2000
O> bject Library Name: Microsoft Access 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msacc9.olb
> Excel 2000
O> bject Library Name: Microsoft Excel 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\excel9.olb
> Outlook 2000
O> bject Library Name: Microsoft Outlook 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msoutl9.olb
>
W> ord 2000
O> bject Library Name: Microsoft Word 9.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office\msword9.olb
> DAO 3.51
O> bject Library Name: Microsoft DAO 3.51 Object Library
F> ile Name and Path: C:\Program Files\Common Files\Microsoft
> Shared\DAO\dao350.dll
> ADO 2.1
O> bject Library Name: Microsoft ActiveX Data Objects 2.1 Library
F> ile Name and Path: C:\Program Files\Common Files\system\ado\msado21.tlb
> Office XP
> Access 2002
O> bject Library Name: Microsoft Access 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10\msacc.olb
> Excel 2002
O> bject Library Name: Microsoft Excel 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10\excel.exe
> Outlook 2002
O> bject Library Name: Microsoft Outlook 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10
\msoutl.olb
> Word 2002
O> bject Library Name: Microsoft Word 10.0 Object Library
F> ile Name and Path: C:\Program Files\Microsoft Office\Office10
\msword.olb
> DAO 3.6
O> bject Library Name: Microsoft DAO 3.6 Object Library
F> ile Name and Path: C:\Program Files\Common Files\Microsoft
> Shared\DAO\dao360.dll
A> DO 2.5
O> bject Library Name: Microsoft ActiveX Data Objects 2.5 Library File
N> ame and Path: C:\Program Files\Common Files\system\ado\msado25.tlb
>
to unsubscribe send a blank email to Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
Message #10 by "Bob Bedell" <bobbedell15@m...> on Sat, 14 Dec 2002 21:12:08 +0000
|
|
Thanx for the generous reply Kenny...much appreciated.
Bob
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
|
|
 |