Help! Getting Error Code 40230 in Access XP when making an mde.

[RWC]

Hello,

I'm having a problem that I'm having a lot of trouble with. I'm running
Access XP, with all the updates, including service pack 2. I'm on a Windows
XP machine. I have a database which I'm trying to make into an MDE, and for
every module I have, I get a Microsoft Visual Basic error "Unexpected Error"
(40230). I've tried decompiling, but that doesn't seem to work. Any ideas
would be greatly appreciated. If you are replying to this post, please
remove the caps and underscores from my email address.

Thanks!
RWC

[Allen Browne]

If a compact/repair (Tools | Database Utilites) doesn't work, and a
decompile (command line switch) doesn't work, the next step would be to
create a new (blank) database and import all the objects.

Make sure the new database is in Access 2002 format: you will not be able to
generate an MDE from A2000 format.

Before importing your objects into the new database, turn off the Name
AutoCorrect boxes under Tools | Options | General.

After importing, open a code window.
Remove any references you don't need. If you are not sure which ones you
need, see:
http://allenbrowne.com/ser-38.html
Then verify that the database compiles correctly. (From a code window: Debug
| Compile). We saw one last week where the compile error showed up only
after the spurious references were removed.

You should now be able to generate the MDE.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"RWC" <he*****************************@shaw.ca> wrote in message
news:AelIb.869588$pl3.851508@pd7tw3no...

Hello,

I'm having a problem that I'm having a lot of trouble with. I'm running
Access XP, with all the updates, including service pack 2. I'm on a Windows XP machine. I have a database which I'm trying to make into an MDE, and for every module I have, I get a Microsoft Visual Basic error "Unexpected Error" (40230). I've tried decompiling, but that doesn't seem to work. Any ideas would be greatly appreciated. If you are replying to this post, please
remove the caps and underscores from my email address.

[Lyle Fairfield]

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:3f**********************@freenews.iinet.net.a u:

Make sure the new database is in Access 2002 format: you will not be
able to generate an MDE from A2000 format.

This can be done with code, but the MDE will run only on machines on which
Access2002 has been installed.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[David W. Fenton]

Mi************@Invalid.Com (Lyle Fairfield) wrote in
<Xn*******************@130.133.1.4>:

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:3f**********************@freenews.iinet.net. au:

Make sure the new database is in Access 2002 format: you will
not be able to generate an MDE from A2000 format.

This can be done with code, but the MDE will run only on machines
on which Access2002 has been installed.

By "this" do you mean generating an A2K MDE with A2K2?

And if so, do you mean that an A2K MDE generated by A2K2 is not
really an A2K MDE, that it won't run in A2K?

Assuming I've interpreted correctly, does this mean that:

1. if you're distributing MDEs to a user base with both A2K and
A2K2, you must compile different MDEs for each user base using the
target version of Access, even though your MDB is A2K format and
would run without difficulty on either version.

2. the A2K compatibility of A2K2 does not extend in any fashion to
MDEs.

I can understand why 2) would be the case -- it would certainly be
consistent with earlier versions of Access and MDEs.

This leads me to a 3rd issue, in the form of a question:

3. does an A2K MDE generated from A2K run in A2K2?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Lyle Fairfield]

dX********@bway.net.invalid (David W. Fenton) wrote in
news:94***************************@24.168.128.78:

Mi************@Invalid.Com (Lyle Fairfield) wrote in
<Xn*******************@130.133.1.4>:

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:3f**********************@freenews.iinet.net .au:

Make sure the new database is in Access 2002 format: you will
not be able to generate an MDE from A2000 format.
This can be done with code, but the MDE will run only on machines
on which Access2002 has been installed.

By "this" do you mean generating an A2K MDE with A2K2?

I mean an ACXP db in AC2K ffile formet.
And if so, do you mean that an A2K MDE generated by A2K2 is not
really an A2K MDE, that it won't run in A2K?
It will run in AC2k (I think) if ACXP is installed on the machine.
Assuming I've interpreted correctly, does this mean that:

1. if you're distributing MDEs to a user base with both A2K and
A2K2, you must compile different MDEs for each user base using the
target version of Access, even though your MDB is A2K format and
would run without difficulty on either version.
Yes.

2. the A2K compatibility of A2K2 does not extend in any fashion to
MDEs.
Sure, you can run these MDEs in ACXP.
3. does an A2K MDE generated from A2K run in A2K2?

Never tried.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[Michael \(michka\) Kaplan [MS]]

"Lyle Fairfield" <Mi************@Invalid.Com> wrote...

1. if you're distributing MDEs to a user base with both A2K and
A2K2, you must compile different MDEs for each user base using the
target version of Access, even though your MDB is A2K format and
would run without difficulty on either version.
Yes.

This is not actually true. I have made all of my add-ins into MDEs in Access
2000 yet they run fine in both Access 2000 and Access 2002.

2. the A2K compatibility of A2K2 does not extend in any fashion to
MDEs.

Sure, you can run these MDEs in ACXP.

Hmmm.... it is the Access 2000 project format and it works perfectly. So it
IS compatible.

3. does an A2K MDE generated from A2K run in A2K2?

Never tried.

I have (see above) and it works just fine.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

[Arno R]

1. if you're distributing MDEs to a user base with both A2K and
A2K2, you must compile different MDEs for each user base using the
target version of Access, even though your MDB is A2K format and
would run without difficulty on either version.

Yes.

For a user base with both A2k-users and A2k2 (Access XP)-users you only need *one* mde.
This must be a A2k-mde in this case. Works allright with Access XP.

Both A2k-mdb's AND A2k-mde's work in Access XP.
******************************************

I recently had a case where a A2k-mde would NOT run in Access XP but this turned out
to be a (difficult to find) corruption-issue .

--
Hope this helps
Arno R

[David W. Fenton]

ar****************@tiscali.nl (Arno R) wrote in
<3f**********************@dreader2.news.tiscali.nl >:

> 1. if you're distributing MDEs to a user base with both A2K
> and A2K2, you must compile different MDEs for each user base
> using the target version of Access, even though your MDB is
> A2K format and would run without difficulty on either version.

Yes.

For a user base with both A2k-users and A2k2 (Access XP)-users you
only need *one* mde. This must be a A2k-mde in this case. Works
allright with Access XP.

Both A2k-mdb's AND A2k-mde's work in Access XP.
******************************************

I recently had a case where a A2k-mde would NOT run in Access XP
but this turned out to be a (difficult to find) corruption-issue .

Does it matter if you create the MDE in A2K or A2K2 (using A2K
format)?

That is, an A2K-created MDE will run in A2K2, but will an A2K MDE
created by A2K2 run in A2K?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Arno R]

David,
As far as I know you can not create a A2k-mde in Access XP.
You can use A2K format but then you can't create mde's, Right?

I can only confirm from own experience what I stated about A2k-mde running in A2k2 .

Arno R
"David W. Fenton" <dX********@bway.net.invalid> schreef in bericht
news:94***************************@24.168.128.78.. .

ar****************@tiscali.nl (Arno R) wrote in
<3f**********************@dreader2.news.tiscali.nl >:

> 1. if you're distributing MDEs to a user base with both A2K
> and A2K2, you must compile different MDEs for each user base
> using the target version of Access, even though your MDB is
> A2K format and would run without difficulty on either version.

Yes.

For a user base with both A2k-users and A2k2 (Access XP)-users you
only need *one* mde. This must be a A2k-mde in this case. Works
allright with Access XP.

Both A2k-mdb's AND A2k-mde's work in Access XP.
******************************************

I recently had a case where a A2k-mde would NOT run in Access XP
but this turned out to be a (difficult to find) corruption-issue .

Does it matter if you create the MDE in A2K or A2K2 (using A2K
format)?

That is, an A2K-created MDE will run in A2K2, but will an A2K MDE
created by A2K2 run in A2K?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Michael \(michka\) Kaplan [MS]]

"David W. Fenton" <dX********@bway.net.invalid> wrote...

Does it matter if you create the MDE in A2K or A2K2 (using A2K
format)?
You cannot create an MDE in Access 2002 of a db in Access 2000 format.
That is, an A2K-created MDE will run in A2K2, but will an A2K MDE
created by A2K2 run in A2K?

The former will, but the latter is not possible.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

[Lyle Fairfield]

"Arno R" <ar****************@tiscali.nl> wrote in
news:3f**********************@dreader2.news.tiscal i.nl:

David,
As far as I know you can not create a A2k-mde in Access XP.
You can use A2K format but then you can't create mde's, Right?

Public Sub CreateADE(ByVal ADPFullPath As String)
Dim a As Access.Application
Set a = New Access.Application
a.SysCmd 603, ADPFullPath, Replace(ADPFullPath, ".adp", ".ade")
Set a = Nothing
End Sub

Just do the adp->mdb and ade->mde mapping.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)