SysCmd 603, "path","path"
The SysCmd is totally undocumented, use at your own risk, if it reformats
your hard drive then just assume that it was time for you clean that machine
off anyway.
Ok, with that said... <g>
You will probably find that it does not work trying to make an MDE of a db
you have just imported objects to or even exported objects from. In fact, it
is recommended that you ALWAYS start a new session of Access via automation
to call it.
Michael
Quote:
> Hi Leonard,
> That's what could happen with undocumented features. <g> The only issue
> that I'm aware of is that you can't make CurrentDB into a MDE this way,
but
> it makes sense.
> As for trouble shooting, probably only someone who knows the internals can
> help you with that. Most of the others will simply be
> shooting-from-the-hip.
> HTH
> --
> Dev Ashish (Just my $.001)
> ---------------
> The Access Web ( http://home.att.net/~dashish )
> ---------------
> :SysCmd 603, "path","path"
> :I found the above solution for creating MDE files from code, in this user
> :group some time ago and have been using it and it has been working
> :perfectly.
> :However recently it sometimes just doesn't work. I am using it in a
module
> :were I transfer some objects from database A into database B then I
> compile
> :the database B, compact B and try to make a MDE from B.
> :I have manually stepped through the code and it just steps over the
SysCmd
> :603 as if it were a comment!
> :Database A is on a Win98 workstation Access97 and database B is on
another
> :Win98 workstation Access97. This whole process runs from the first
> :workstation, database A.
> :Is there any way to trouble shoot this? I can find absolutely no
> information
> :or help for SysCmd 603?!
> :Thanks in advance!
> :
> :