471,072 Members | 1,389 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,072 software developers and data experts.

Acess2000 vs Access2003

Hoping someonce can tell me what compatibility problems I might run
into when I have to have my Access Project developed on Access2K run
in a user environment where users are using Access2003 as well as
Access2000.
I have already seen a problem where if I open my project using
Access2003 and save any objects, then run it on Access2000, I
encounter "Bad DLL Calling Convention error..." on the Access2K
machines. If I never open and save the database on Access 2003 before
distributing it, I do not get this error.
Are thre any other things I should know about?
Thanks,
lq
Nov 13 '05 #1
9 2272
I recently worked on an Access Project (ADP) distributed in Access 2000 (the
client's development machine and users only had Office 2000 Pro installed).
I did some of the work on my notebook in Access 2002 or 2003 (both of which
I have installed). The only "problem" I encountered was with the
references -- which had to be revised to avoid compile errors (they were the
interfaces to Word and Excel).

I did not experience the error you describe.

Larry Linson
Microsoft Access MVP

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Hoping someonce can tell me what compatibility problems I might run
into when I have to have my Access Project developed on Access2K run
in a user environment where users are using Access2003 as well as
Access2000.
I have already seen a problem where if I open my project using
Access2003 and save any objects, then run it on Access2000, I
encounter "Bad DLL Calling Convention error..." on the Access2K
machines. If I never open and save the database on Access 2003 before
distributing it, I do not get this error.
Are thre any other things I should know about?
Thanks,
lq

Nov 13 '05 #2
As well as the references issue Larry raises, you can receive the "Bad DLL"
message if the database is partially corrupt, which is quite common if the
A2000 machine does not have all serrice. packs.

Suggestions.
1. If you do not already have them, go to support.microsoft.com, Downloads
section, and get SP3 for Office 2000 and SP8 for JET 4. Both are absolutely
essential.

2. After applying the service packs, and making a backup copy of your
database, compact it (Tools | Database Utilities | Compact). Then close
Access, and decompile it by entering something like this at the command
prompt. It's all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

3. Uncheck the boxes under Tools | Options | General | Name AutoCorrect. For
an explanation, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
Then compact again.

4. Check that the application still compiles. If so, you should find it now
works with A2003 also.

Note that A2000 and A2003 use different binaries. That is, when you open an
A2003 mdb in A2000 becomes uncompiled.

--
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.

"Larry Linson" <bo*****@localhost.not> wrote in message
news:fH*******************@nwrddc01.gnilink.net...
I recently worked on an Access Project (ADP) distributed in Access 2000 (the client's development machine and users only had Office 2000 Pro installed). I did some of the work on my notebook in Access 2002 or 2003 (both of which I have installed). The only "problem" I encountered was with the
references -- which had to be revised to avoid compile errors (they were the interfaces to Word and Excel).

I did not experience the error you describe.

Larry Linson
Microsoft Access MVP

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Hoping someonce can tell me what compatibility problems I might run
into when I have to have my Access Project developed on Access2K run
in a user environment where users are using Access2003 as well as
Access2000.
I have already seen a problem where if I open my project using
Access2003 and save any objects, then run it on Access2000, I
encounter "Bad DLL Calling Convention error..." on the Access2K
machines. If I never open and save the database on Access 2003 before
distributing it, I do not get this error.
Are thre any other things I should know about?
Thanks,
lq

Nov 13 '05 #3
Allen,
In my Access2K Tools | Options | General | Name AutoCorrect does not
exist.
I am running SR1 on this development machine to keep compatibility
with a client site that refuse to install SP3 on 500+ machines. (I
know, don't get me started on that - it was like pulling teeth to get
them to do SR-1)
Is Name AutoCorrect a feature that is not installed until SP3?
Also, is is possible to turn that off using Application.SetOption?
lq

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
As well as the references issue Larry raises, you can receive the "Bad DLL"
message if the database is partially corrupt, which is quite common if the
A2000 machine does not have all serrice. packs.

Suggestions.
1. If you do not already have them, go to support.microsoft.com, Downloads
section, and get SP3 for Office 2000 and SP8 for JET 4. Both are absolutely
essential.

2. After applying the service packs, and making a backup copy of your
database, compact it (Tools | Database Utilities | Compact). Then close
Access, and decompile it by entering something like this at the command
prompt. It's all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

3. Uncheck the boxes under Tools | Options | General | Name AutoCorrect. For
an explanation, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
Then compact again.

4. Check that the application still compiles. If so, you should find it now
works with A2003 also.

Note that A2000 and A2003 use different binaries. That is, when you open an
A2003 mdb in A2000 becomes uncompiled.

--
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.

"Larry Linson" <bo*****@localhost.not> wrote in message
news:fH*******************@nwrddc01.gnilink.net...
I recently worked on an Access Project (ADP) distributed in Access 2000

(the
client's development machine and users only had Office 2000 Pro

installed).
I did some of the work on my notebook in Access 2002 or 2003 (both of

which
I have installed). The only "problem" I encountered was with the
references -- which had to be revised to avoid compile errors (they were

the
interfaces to Word and Excel).

I did not experience the error you describe.

Larry Linson
Microsoft Access MVP

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Hoping someonce can tell me what compatibility problems I might run
into when I have to have my Access Project developed on Access2K run
in a user environment where users are using Access2003 as well as
Access2000.
I have already seen a problem where if I open my project using
Access2003 and save any objects, then run it on Access2000, I
encounter "Bad DLL Calling Convention error..." on the Access2K
machines. If I never open and save the database on Access 2003 before
distributing it, I do not get this error.
Are thre any other things I should know about?
Thanks,
lq

Nov 13 '05 #4
The Name AutoCorrect problems are there in A2k, even without any service
packs.

If they are not showing, try resetting your menu: right-click to the right
of the menu bar, and choose Customize.

Programmatically, you should be able to GetOption and SetOption with these
names:
Application.GetOption("Perform Name AutoCorrect")
Application.GetOption("Log Name AutoCorrect Changes")
Application.GetOption("Track Name AutoCorrect Info")

--
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.

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Allen,
In my Access2K Tools | Options | General | Name AutoCorrect does not
exist.
I am running SR1 on this development machine to keep compatibility
with a client site that refuse to install SP3 on 500+ machines. (I
know, don't get me started on that - it was like pulling teeth to get
them to do SR-1)
Is Name AutoCorrect a feature that is not installed until SP3?
Also, is is possible to turn that off using Application.SetOption?
lq

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
As well as the references issue Larry raises, you can receive the "Bad DLL" message if the database is partially corrupt, which is quite common if the A2000 machine does not have all serrice. packs.

Suggestions.
1. If you do not already have them, go to support.microsoft.com, Downloads section, and get SP3 for Office 2000 and SP8 for JET 4. Both are absolutely essential.

2. After applying the service packs, and making a backup copy of your
database, compact it (Tools | Database Utilities | Compact). Then close
Access, and decompile it by entering something like this at the command
prompt. It's all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

3. Uncheck the boxes under Tools | Options | General | Name AutoCorrect. For an explanation, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
Then compact again.

4. Check that the application still compiles. If so, you should find it now works with A2003 also.

Note that A2000 and A2003 use different binaries. That is, when you open an A2003 mdb in A2000 becomes uncompiled.

Nov 13 '05 #5
"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Allen,
In my Access2K Tools | Options | General | Name AutoCorrect does not
exist.
I am running SR1 on this development machine to keep compatibility
with a client site that refuse to install SP3 on 500+ machines. (I
know, don't get me started on that - it was like pulling teeth to get
them to do SR-1)
Is Name AutoCorrect a feature that is not installed until SP3?
Also, is is possible to turn that off using Application.SetOption?
lq


I also have Access 2000 SR1 and it is right there in the upper right of the
general tab. What do you have in that space, nothing?
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #6

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Hoping someonce can tell me what compatibility problems I might run
into when I have to have my Access Project developed on Access2K run
in a user environment where users are using Access2003 as well as
Access2000.
I have already seen a problem where if I open my project using
Access2003 and save any objects, then run it on Access2000, I
encounter "Bad DLL Calling Convention error..." on the Access2K
machines. If I never open and save the database on Access 2003 before
distributing it, I do not get this error.
Are thre any other things I should know about?
Thanks,
lq

is bad becuase no service paks!

*Sherwood Wang MVP*
Nov 13 '05 #7
Rick,
In the left column I have:
Left Margin,
Right Margin,
Top Margin,
Bottom Margin.
To the right of that, above: "Use four-digit year formatting, I have a
lovely field of middle gray with nothing in it.
I tried monkeying with the toolbar but see no way of changing the
options displayed, even though I have shown/hidden/shown it and
clicked "restore defaults."
lq
"Rick Brandt" <ri*********@hotmail.com> wrote in message news:<2m************@uni-berlin.de>...
"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Allen,
In my Access2K Tools | Options | General | Name AutoCorrect does not
exist.
I am running SR1 on this development machine to keep compatibility
with a client site that refuse to install SP3 on 500+ machines. (I
know, don't get me started on that - it was like pulling teeth to get
them to do SR-1)
Is Name AutoCorrect a feature that is not installed until SP3?
Also, is is possible to turn that off using Application.SetOption?
lq


I also have Access 2000 SR1 and it is right there in the upper right of the
general tab. What do you have in that space, nothing?

Nov 13 '05 #8
Allen,
Should all three of these be set to false in a working environment?
lq

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
The Name AutoCorrect problems are there in A2k, even without any service
packs.

If they are not showing, try resetting your menu: right-click to the right
of the menu bar, and choose Customize.

Programmatically, you should be able to GetOption and SetOption with these
names:
Application.GetOption("Perform Name AutoCorrect")
Application.GetOption("Log Name AutoCorrect Changes")
Application.GetOption("Track Name AutoCorrect Info")

--
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.

"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Allen,
In my Access2K Tools | Options | General | Name AutoCorrect does not
exist.
I am running SR1 on this development machine to keep compatibility
with a client site that refuse to install SP3 on 500+ machines. (I
know, don't get me started on that - it was like pulling teeth to get
them to do SR-1)
Is Name AutoCorrect a feature that is not installed until SP3?
Also, is is possible to turn that off using Application.SetOption?
lq

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
As well as the references issue Larry raises, you can receive the "Bad DLL" message if the database is partially corrupt, which is quite common if the A2000 machine does not have all serrice. packs.

Suggestions.
1. If you do not already have them, go to support.microsoft.com, Downloads section, and get SP3 for Office 2000 and SP8 for JET 4. Both are absolutely essential.

2. After applying the service packs, and making a backup copy of your
database, compact it (Tools | Database Utilities | Compact). Then close
Access, and decompile it by entering something like this at the command
prompt. It's all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

3. Uncheck the boxes under Tools | Options | General | Name AutoCorrect. For an explanation, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
Then compact again.

4. Check that the application still compiles. If so, you should find it now works with A2003 also.

Note that A2000 and A2003 use different binaries. That is, when you open an A2003 mdb in A2000 becomes uncompiled.

Nov 13 '05 #9
Definately.

--
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.
"Lauren Quantrell" <la*************@hotmail.com> wrote in message
news:47**************************@posting.google.c om...
Allen,
Should all three of these be set to false in a working environment?
lq

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
The Name AutoCorrect problems are there in A2k, even without any service
packs.

If they are not showing, try resetting your menu: right-click to the right of the menu bar, and choose Customize.

Programmatically, you should be able to GetOption and SetOption with these names:
Application.GetOption("Perform Name AutoCorrect")
Application.GetOption("Log Name AutoCorrect Changes")
Application.GetOption("Track Name AutoCorrect Info")

Nov 13 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Dennis | last post: by
6 posts views Thread by Ryan Bounds | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.