.MDA files to Access 2007

[SpaceMarine]

hello,

does anyone know how to convert Access 2000 .MDA files to the Access
2007 equivalent? ive been able to convert .MDB files to .ACCDB, but
not MDAs.

im new to Access, and have been asked by my project manager to perform
this task. (we are converting our legacy Access 2000 application to
Access 2007).

if if makes a difference, in 2000 we used a .MDW to help open
the .MDA. then we compiled the MDA into a .MDE. this was then used as
a reference by something else. that is what we would like to replicate
here... but the first step seems to be getting the .MDA into the
Access 2007 format. i may be mistaken.


thanks!
sm

 

[Arvin Meyer [MVP]]

Your best bet is to leave everything alone and not use the new format unless
the new features of that format are required. By leaving everything in the
Access 2000 format, everything will work in every version from 2000 to the
present.

To answer your question, try renaming the MDA to MDB and converting that.

 

[SpaceMarine]

Your best bet is to leave everything alone and not use the new format unless
the new features of that format are required. By leaving everything in the
Access 2000 format, everything will work in every version from 2000 to the
present.

heh...in theory. if it worked seemlessly as-is we wouldnt be trying to
convert these pieces.

To answer your question, try renaming the MDA to MDB and converting that.

will try.


thanks
sm

 

[David W. Fenton]

To answer your question, try renaming the MDA to MDB and
converting that.

MDA files may actually be MDEs, though.

 

[SpaceMarine]

Your best bet is to leave everything alone and not use the new format unless
the new features of that format are required. By leaving everything in the
Access 2000 format, everything will work in every version from 2000 to the
present.

got the 411 on why we arent leaving everything as-is.

1) when opening the .MDB in Access 2007, we werent able to locate the
VBA code or references. after converting the .mdb to a .accdb we could
(by opening any Module in "Design View", which produces the VB6 IDE).
could be just a training issue.

2) the more serious is one of our .MDAs is no longer responding. im
not an expert on this application's design, but ive been told the .MDA
in question makes use of a .MDW in order do user authentication. we
use a little shortcut like so:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\apps
\someLibrary.mda" /wrkgrp "Q:\apps\foo.mdw"

....which on Windows 2000 & Access 2000 opened an authentication logon
window for Name & Password. problem in Vista & Access 2007 (our new
platform im testing on) is, this authentication window opens, and it
correctly validates passwords, but after submitting the proper
password....nothing happens. the prompt vanishes, leaving a generic-
application-window open. nothing further loads.

so we thought perhaps by converting the failing .MDA to a newer
version it may start working again.

To answer your question, try renaming the MDA to MDB and converting that.

i cant do this. because the MDA uses authentication.. trying to open
it straight-up (w/o the MDW as shown above) produces: "You do not have
the necessary permissions to the use [path] object. Have your system
administrator or the person who created this object establish the
appropiate permissions for you." i am running this as an admin, so i
dont think its a file thing.. i believe its the lack of passing
credentials into it.


any thoughts? thanks!
sm

 

[SpaceMarine]

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\apps
\someLibrary.mda" /wrkgrp "Q:\apps\foo.mdw"

...which on Windows 2000 & Access 2000 opened an authentication logon
window for Name & Password. problem in Vista & Access 2007 (our new
platform im testing on) is, this authentication window opens, and it
correctly validates passwords, but after submitting the proper
password....nothing happens. the prompt vanishes, leaving a generic-
application-window open. nothing further loads.

....i just realized... this could be a simple matter of Access 2007's
path not being the above. the above exists, but im not sure its the
real path to Access 2007, which may be "C:\Program Files\Microsoft
Office\Office12\MSACCESS.EXE". going to check this out...


sm

 

[SpaceMarine]

...i just realized... this could be a simple matter of Access 2007's
path not being the above. the above exists, but im not sure its the
real path to Access 2007, which may be "C:\Program Files\Microsoft
Office\Office12\MSACCESS.EXE". going to check this out...

yep. after updating the login shortcut to the "real" Access 2007 path,
i can get into the MDA post-authentication. gives me a busted
reference message, but i can work on that....

closer!


sm

 

[SpaceMarine]

yep. after updating the login shortcut to the "real" Access 2007 path,
i can get into the MDA post-authentication. gives me a busted
reference message, but i can work on that....

closer!

finished. fixed the reference, decoded the MDA database, enabled
trust, and was able to make it a ".accde" file. cool.


thanks!
sm