Access 2003 to 2000 mde

[David Shorthouse]

Hello folks,

As I understand it, an mde created in Access 2003 will not work with an
Access 2000 client. Correct? I have been hunting for a solution to create an
mde that won't exclude all potential Access 2000, 2002, and 2003 clients and
came across MDE 2000 (http://www.rvsoftware.hr/mde2000.htm). Can anyone
vouch for its functionality or offer another solution for me? Please note
that I do not wish to install Access 2000 on my production machine.

Dave

 

[Douglas J. Steele]

Never heard of them before.

 

[David Shorthouse]

Since you sound knowledgeable about these sorts of conversions, do you know
if ADE 2003 can convert an Access 2000 mdb to an Access 2000 mde? Of course,
I can make an mde from Access 2003, but this will eliminate half my
potential client base because they are using Access 2000.

Dave

--
______________________________
Remove "_SPAM" to reply directly.

Never heard of them before.

 

[Rick Brandt]

Since you sound knowledgeable about these sorts of conversions, do
you know if ADE 2003 can convert an Access 2000 mdb to an Access 2000
mde? Of course, I can make an mde from Access 2003, but this will
eliminate half my potential client base because they are using Access
2000.

So why don't you make the MDE with 2000? That will work on all versions above.

If you have a "client base" then you are doing this for a living. If that is
true you should own every version.

 

[Albert D.Kallal]

I never herd of the product.

I was under the impression that if you made a a2000 mde, then it would work
with all three versions. Without question, as a general rule, you have to
use the same version to make a mde, and this utility gives a workaround.

I should note that I have perfectly well functioning applications in a2003
that when converted to a2000, and compiled as a mde they exhibited a whole
bunch of problems. These problems were due to the fact that a a2003 has a
LOT of fixes in terms of thread, and event order (especially for things like
conditional formatting). The ONLY fix in this case was to test, and check
the software on the a2000 box. I had to modify

So, really, because of compatibility issues, I would develop on the lowest
common machine.

You have to realize that you cant install a ms-access applications made
today on a old 1985 computer (it is not even running windows, and likely
does not even have a mouse!). However, what is rather amazing is that most
software from that 1985 machine can run on a BRAND new machine. So, as a
industry observation, for the last 20 years we are as a general rule able to
move software forward in time, but not backwards, and that is what you are
attempting to do.

The correct approach here should be obvious: Develop to the oldest standard,
and then move forward...as that is how the whole industry has generally
worked.

And, you could install a2000, as many ms-access developers have 2, 3 or even
4 versions of ms-access installed on the one machine.

For me, I all a2003, and for older clients, I simply deploy using the
runtime. (this works well as long as they don't have any other access
applications).

 

['69 Camaro]

Hi, David.

I've never used their product, but it's certainly doable. The company I
work for sells the very simple instructions and source code to Access
developers so that they can use the MDE 2K creation utility in their own
applications. The VBA subroutine creates Access 2000 MDE files no matter
whether the user is running Access 2000, 2002, or 2003. I imagine RV
Software's utility does, too, except they don't offer the source code.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

 

[David Shorthouse]

No, I am not doing this for a living. If I were, I probably would know the
answer to this already and wouldn't need to resort to an ng. I have one
small need and am merely requesting some assistance.

Dave