Re: Possible Fix for "Unable to create MDE" Error and "Unexpected Error 40230" in Access 2002
- From: "Mark" <m_a_potter@xxxxxxxxxxx>
- Date: Wed, 25 Jan 2006 08:55:06 -0000
Following my post yesterday Access froze whilst I was debugging some code
and would not subsequently create an MDE file again with multiple Error
40230 messages.
Just to clarify, this is a front end db and the code compiles ok without any
problems even though the MDE creation fails.
The resolution this time required a slightly different sequence;
Copy FE db to a local disk
Decompile
*Did NOT then re-compile the code*
Successfully made an MDE
Compiled code (in FE)
C&R FE db
Moved FE back to network drive
Then FE created MDE OK there too
*I first tried compiling the code straight after a decompile but this didn't
fix the problem.
The above isn't very scientific but did allow me to recover my db (again) so
might help others also.
Whilst importing everything into another mdb is an option it is actually a
*very last resort* for me as the db is huge with complex security - no small
task.
Regards
Mark Potter
"Albert D.Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in message
news:u5h9DcWIGHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
> The fact that after all was said and done..you find that you can compile
> the code, and build the mde when it is on the shared folder.
>
> It is possible that some references was still stray. (remember, you can
> actually make references to other mde files..and the LOCAL directory is
> searched first for these references).
>
> I also would have consider creating a blank mdb file..and importing
> everything. This would reduce/eliminate references issues, and also fixes
> forms of corruption.
>
> So, there are in some cases some different behaviors here. It is not
> really clear if that actually copying the mdb to your local machine fixed
> a reference, and allowed the code to compile, or some other issue.
>
> Of course...as always..you need to do a debug->compile in your code and
> make sure no code errors occur BEFORE you attempt to make the
> mde-xecutable file.
>
> However, since the application did allow you to build the mde when working
> on the local machine, then something must have changed.
>
> In addition to the above, it needs pointing out that you MUST run the
> front end part of the application on each pc..or you will experience
> general problems if this is to be used by more then one person. This
> should come as NO surprise here, and is standard fair for any developer.
>
> I explain why you split here.....
>
> http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal@xxxxxxx
> http://www.members.shaw.ca/AlbertKallal
>
>
.
- References:
- Prev by Date: Re: Possible Fix for "Unable to create MDE" Error and "Unexpected Error 40230" in Access 2002
- Next by Date: Re: Object Dependencies
- Previous by thread: Re: Possible Fix for "Unable to create MDE" Error and "Unexpected Error 40230" in Access 2002
- Next by thread: Object Dependencies
- Index(es):
Relevant Pages
|
Loading
