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
9  2395 
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
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
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
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.
"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
"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*
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?
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.
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")
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Dennis |
last post by:
If I create a database in AccessXP-2000mode, can someone with Access2003 run it?
Do either of us have to do anything special?
Thanks!
Dennis
|
by: mariantrygg |
last post by:
Hi
I have an app that uses the a2K run-time. I have just discovered that
installing this app breaks an access2003 installation causing the user
to have to repair the installation using the...
|
by: dynfax |
last post by:
When I use Access 97 with Terminal Services, and the terminal window is
minimized, the popup form displays - and when i reset the focus to the
terminal window the popup form displays.
In...
|
by: Ryan Bounds |
last post by:
Hi All
We have upgraded from Access2000 to Access2003 with all service packs.
The problem that we have is: When a user try's to filter a client the
database crashes and close's Access2003,...
|
by: Zlatko Matić |
last post by:
Hello.
Could somebody explain the following situation:
I have a .mdb on my notebook with Windows XP SP2 and Access 2003. I prepared
..mde and tried to use it on another computer with Windows XP...
|
by: 2D Rick |
last post by:
With the help from members in the VB forum I've pieced together code
that works in VB6 to create radial text similar to "text on a path"
seen in graphics programs.(on a circle only)
I use an...
|
by: Vera |
last post by:
I built a class in VB.NET that has an overloaded constructor. It can either accept nothing, a string or an object
Public Sub New(
MyBase.New(
End Su
Public Sub New(ByVal strName As String...
|
by: usenet |
last post by:
How and where can one find out about the basics of VB/Access2003
syntax?
I am a died in the wool C/C++/Java Linux/Unix programmer and I am
finding it difficult to understand the program format...
|
by: Ramchandar |
last post by:
Hi,
I am creating reports using VBA code.
I have the same query in a querydef residing both in Access97 and Access2003. The result of this querydef is then moved to a table in Access97 and...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
| |
