Can someone familiar with Access 2003 please answer this question? I am
asking because I don't have the use of A2003. When Access 2003 finds an
Access 2000 database, does it come up with some sort of question/suggestion
indicating that you can convert this datbase into the new format? I am
trying to trouble shoot a remote site where a big error message indicating
the database was converted using the wrong method comes up when they try to
open an Access 2000 database with either Access 2000 or Access 2002. AFAIK,
there may be a small number of computers on-site using Acess 2003. Is it
possible that someone has inadvertently converted the database into a format
unreadable by earlier copies of Access?
I thought of corruption, but this has happened to 2 different databases on
the same site in less than 2 weeks! Co-incidence?
dixie
12  2193 
Access 2003 can use the A2000 database format without conversion.
The question, "Do you want to Open or Convert?" occurs if you try to open an
Access 97 in any version from 2000 onwards.
Acess 2003 does use a different binary for the compiled code than A2000.
This process is not perfect, so if you open the database in A2003 modify the
forms/reports/module, save, and then open them in A2000 you can get
corruption issues.
For developers, the workaround is:
1. Decompile the database before, i.e. enter something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"
2. Compact.
3. Open in the other version, and Compile.
For end users, you provide each workstation with its own local copy of the
front end, compiled under the version not later than what they use. For
example, create the MDE in Access 2000 and give copies to each user.
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******** @duster.adelaid e.on.net... Can someone familiar with Access 2003 please answer this question? I am
asking because I don't have the use of A2003. When Access 2003 finds an
Access 2000 database, does it come up with some sort of
question/suggestion indicating that you can convert this datbase into the
new format? I am trying to trouble shoot a remote site where a big error
message indicating the database was converted using the wrong method comes
up when they try to open an Access 2000 database with either Access 2000
or Access 2002. AFAIK, there may be a small number of computers on-site
using Acess 2003. Is it possible that someone has inadvertently converted
the database into a format unreadable by earlier copies of Access?
I thought of corruption, but this has happened to 2 different databases on
the same site in less than 2 weeks! Co-incidence?
dixie
What about mde's Allen, obviously can't do this on-site with them. But,
surely if I decompile before I compile, the problem is less likely to arise.
This is the first time this has ever happened and it is twice at the same
site in 2 weeks. They use a mixture of 2000/XP/2003 (probably with a
mixture of Service Packs applied too!) I could do special versions for each
program I guess, but it seems like a lot of trouble. I know that A2003
can't produce an mde for 2002 or 2000, so I guess that means I would need
all 3 programs. Sorry, I am rambling. Thinking out aloud.
Thanks for your help.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Access 2003 can use the A2000 database format without conversion.
The question, "Do you want to Open or Convert?" occurs if you try to open
an Access 97 in any version from 2000 onwards.
Acess 2003 does use a different binary for the compiled code than A2000.
This process is not perfect, so if you open the database in A2003 modify
the forms/reports/module, save, and then open them in A2000 you can get
corruption issues.
For developers, the workaround is:
1. Decompile the database before, i.e. enter something like this at the
command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"
2. Compact.
3. Open in the other version, and Compile.
For end users, you provide each workstation with its own local copy of the
front end, compiled under the version not later than what they use. For
example, create the MDE in Access 2000 and give copies to each user.
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******** @duster.adelaid e.on.net... Can someone familiar with Access 2003 please answer this question? I am
asking because I don't have the use of A2003. When Access 2003 finds an
Access 2000 database, does it come up with some sort of
question/suggestion indicating that you can convert this datbase into the
new format? I am trying to trouble shoot a remote site where a big error
message indicating the database was converted using the wrong method
comes up when they try to open an Access 2000 database with either Access
2000 or Access 2002. AFAIK, there may be a small number of computers
on-site using Acess 2003. Is it possible that someone has inadvertently
converted the database into a format unreadable by earlier copies of
Access?
I thought of corruption, but this has happened to 2 different databases
on the same site in less than 2 weeks! Co-incidence?
dixie
The A2000 MDE should be fine on Access 2002 and Access 2003. Further, it
cannot decompile, so it should not corrupt at the VBA level. Of course,
other kinds of corruption can still occur, such as those caused by Name
AutoCorrupt: http://members.iinet.net.au/~allenbrowne/bug-03.html
Unless you are creating runtime installations, you should not have to worry
about the version of Windows on the users' machines. You do want the know
the user's version of Office, service pack, *and* JET service pack. What we
do is include a couple of text boxes on the form you use for Help | About,
like this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
The function calls are from: http://www.mvps.org/access/api/api0065.htm http://www.mvps.org/access/api/api0054.htm
Completely different thought, but there is an incredibly stupid set of
dialog boxes the user can see in A2003 when they try to open a file. It
warns the user that the file may be unsafe to open and not to do it. If they
say, "Do it anyway", they are then presented with another dialog warning
that unsafe expressions are not blocked. It's quite a complicated dialog
with long messages and scrollbars, and it's hard to even find the question
you are answering, but again they have to go against the Microsoft
recommendation and choose the non-default answer. Then they receive a
*third* warning that they really should not do this! And this happens every
time they open the database! If Microsoft were trying to destrory Access,
they could hardly have come up with a more effective strategy.
The A2003 user can avoid this recurring if they set their Macro Security
setting to Low, again something MS specifically recommends against. Don't
ask me why this garbage is in there, but could it be these dialogs that are
tripping up your users?
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... What about mde's Allen, obviously can't do this on-site with them. But,
surely if I decompile before I compile, the problem is less likely to
arise. This is the first time this has ever happened and it is twice at
the same site in 2 weeks. They use a mixture of 2000/XP/2003 (probably
with a mixture of Service Packs applied too!) I could do special versions
for each program I guess, but it seems like a lot of trouble. I know that
A2003 can't produce an mde for 2002 or 2000, so I guess that means I would
need all 3 programs. Sorry, I am rambling. Thinking out aloud.
Thanks for your help.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Access 2003 can use the A2000 database format without conversion.
The question, "Do you want to Open or Convert?" occurs if you try to open
an Access 97 in any version from 2000 onwards.
Acess 2003 does use a different binary for the compiled code than A2000.
This process is not perfect, so if you open the database in A2003 modify
the forms/reports/module, save, and then open them in A2000 you can get
corruption issues.
For developers, the workaround is:
1. Decompile the database before, i.e. enter something like this at the
command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"
2. Compact.
3. Open in the other version, and Compile.
For end users, you provide each workstation with its own local copy of
the front end, compiled under the version not later than what they use.
For example, create the MDE in Access 2000 and give copies to each user.
"dixie" <di***@dogmail. com> wrote in message
news:41******** @duster.adelaid e.on.net... Can someone familiar with Access 2003 please answer this question? I am
asking because I don't have the use of A2003. When Access 2003 finds an
Access 2000 database, does it come up with some sort of
question/suggestion indicating that you can convert this datbase into
the new format? I am trying to trouble shoot a remote site where a big
error message indicating the database was converted using the wrong
method comes up when they try to open an Access 2000 database with
either Access 2000 or Access 2002. AFAIK, there may be a small number
of computers on-site using Acess 2003. Is it possible that someone has
inadvertently converted the database into a format unreadable by earlier
copies of Access?
I thought of corruption, but this has happened to 2 different databases
on the same site in less than 2 weeks! Co-incidence?
dixie
Firstly about this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I entered them as the source of two text boxes and it only returned me
#Name? What have I done wrong here - I am using Access 2000 - SP3.
_______________ _____________
Your post is very informative Allen. It seems to me that with each new
version of Office or Windows, Microsoft want to control things more tightly.
What they fail to realise (or dont care) is that the poor users of their
software are not all programmers or IT wizards, just normal joe blow and
Jane Citizen doing their everyday work. The registry change needed to do
automated mailmerge from Access to Word 2003 is a good example. Sending
people a registry patch with instructions on how to apply it is not the
easiest thing to achieve. Some of the people involved do not even know what
the registry is!
Again, thanks for your insightful reply.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... The A2000 MDE should be fine on Access 2002 and Access 2003. Further, it
cannot decompile, so it should not corrupt at the VBA level. Of course,
other kinds of corruption can still occur, such as those caused by Name
AutoCorrupt:
http://members.iinet.net.au/~allenbrowne/bug-03.html
Unless you are creating runtime installations, you should not have to
worry about the version of Windows on the users' machines. You do want the
know the user's version of Office, service pack, *and* JET service pack.
What we do is include a couple of text boxes on the form you use for Help
| About, like this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
The function calls are from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0054.htm
Completely different thought, but there is an incredibly stupid set of
dialog boxes the user can see in A2003 when they try to open a file. It
warns the user that the file may be unsafe to open and not to do it. If
they say, "Do it anyway", they are then presented with another dialog
warning that unsafe expressions are not blocked. It's quite a complicated
dialog with long messages and scrollbars, and it's hard to even find the
question you are answering, but again they have to go against the
Microsoft recommendation and choose the non-default answer. Then they
receive a *third* warning that they really should not do this! And this
happens every time they open the database! If Microsoft were trying to
destrory Access, they could hardly have come up with a more effective
strategy.
The A2003 user can avoid this recurring if they set their Macro Security
setting to Low, again something MS specifically recommends against. Don't
ask me why this garbage is in there, but could it be these dialogs that
are tripping up your users?
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... What about mde's Allen, obviously can't do this on-site with them. But,
surely if I decompile before I compile, the problem is less likely to
arise. This is the first time this has ever happened and it is twice at
the same site in 2 weeks. They use a mixture of 2000/XP/2003 (probably
with a mixture of Service Packs applied too!) I could do special
versions for each program I guess, but it seems like a lot of trouble. I
know that A2003 can't produce an mde for 2002 or 2000, so I guess that
means I would need all 3 programs. Sorry, I am rambling. Thinking out
aloud.
Thanks for your help.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Access 2003 can use the A2000 database format without conversion.
The question, "Do you want to Open or Convert?" occurs if you try to
open an Access 97 in any version from 2000 onwards.
Acess 2003 does use a different binary for the compiled code than A2000.
This process is not perfect, so if you open the database in A2003 modify
the forms/reports/module, save, and then open them in A2000 you can get
corruption issues.
For developers, the workaround is:
1. Decompile the database before, i.e. enter something like this at the
command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"
2. Compact.
3. Open in the other version, and Compile.
For end users, you provide each workstation with its own local copy of
the front end, compiled under the version not later than what they use.
For example, create the MDE in Access 2000 and give copies to each user.
"dixie" <di***@dogmail. com> wrote in message
news:41******** @duster.adelaid e.on.net...
Can someone familiar with Access 2003 please answer this question? I
am asking because I don't have the use of A2003. When Access 2003
finds an Access 2000 database, does it come up with some sort of
question/suggestion indicating that you can convert this datbase into
the new format? I am trying to trouble shoot a remote site where a big
error message indicating the database was converted using the wrong
method comes up when they try to open an Access 2000 database with
either Access 2000 or Access 2002. AFAIK, there may be a small number
of computers on-site using Acess 2003. Is it possible that someone has
inadvertently converted the database into a format unreadable by
earlier copies of Access?
I thought of corruption, but this has happened to 2 different databases
on the same site in less than 2 weeks! Co-incidence?
dixie
Did you copy the functions from the mvps.org links?
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... Firstly about this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I entered them as the source of two text boxes and it only returned me
#Name? What have I done wrong here - I am using Access 2000 - SP3.
_______________ _____________
Your post is very informative Allen. It seems to me that with each new
version of Office or Windows, Microsoft want to control things more
tightly. What they fail to realise (or dont care) is that the poor users
of their software are not all programmers or IT wizards, just normal joe
blow and Jane Citizen doing their everyday work. The registry change
needed to do automated mailmerge from Access to Word 2003 is a good
example. Sending people a registry patch with instructions on how to
apply it is not the easiest thing to achieve. Some of the people involved
do not even know what the registry is!
Again, thanks for your insightful reply.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... The A2000 MDE should be fine on Access 2002 and Access 2003. Further, it
cannot decompile, so it should not corrupt at the VBA level. Of course,
other kinds of corruption can still occur, such as those caused by Name
AutoCorrupt:
http://members.iinet.net.au/~allenbrowne/bug-03.html
Unless you are creating runtime installations, you should not have to
worry about the version of Windows on the users' machines. You do want
the know the user's version of Office, service pack, *and* JET service
pack. What we do is include a couple of text boxes on the form you use
for Help | About, like this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
The function calls are from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0054.htm
Completely different thought, but there is an incredibly stupid set of
dialog boxes the user can see in A2003 when they try to open a file. It
warns the user that the file may be unsafe to open and not to do it. If
they say, "Do it anyway", they are then presented with another dialog
warning that unsafe expressions are not blocked. It's quite a complicated
dialog with long messages and scrollbars, and it's hard to even find the
question you are answering, but again they have to go against the
Microsoft recommendation and choose the non-default answer. Then they
receive a *third* warning that they really should not do this! And this
happens every time they open the database! If Microsoft were trying to
destrory Access, they could hardly have come up with a more effective
strategy.
The A2003 user can avoid this recurring if they set their Macro Security
setting to Low, again something MS specifically recommends against. Don't
ask me why this garbage is in there, but could it be these dialogs that
are tripping up your users?
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... What about mde's Allen, obviously can't do this on-site with them. But,
surely if I decompile before I compile, the problem is less likely to
arise. This is the first time this has ever happened and it is twice at
the same site in 2 weeks. They use a mixture of 2000/XP/2003 (probably
with a mixture of Service Packs applied too!) I could do special
versions for each program I guess, but it seems like a lot of trouble.
I know that A2003 can't produce an mde for 2002 or 2000, so I guess that
means I would need all 3 programs. Sorry, I am rambling. Thinking out
aloud.
Thanks for your help.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
Access 2003 can use the A2000 database format without conversion.
The question, "Do you want to Open or Convert?" occurs if you try to
open an Access 97 in any version from 2000 onwards.
Acess 2003 does use a different binary for the compiled code than
A2000. This process is not perfect, so if you open the database in
A2003 modify the forms/reports/module, save, and then open them in
A2000 you can get corruption issues.
For developers, the workaround is:
1. Decompile the database before, i.e. enter something like this at the
command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"
2. Compact.
3. Open in the other version, and Compile.
For end users, you provide each workstation with its own local copy of
the front end, compiled under the version not later than what they use.
For example, create the MDE in Access 2000 and give copies to each
user.
"dixie" <di***@dogmail. com> wrote in message
news:41******** @duster.adelaid e.on.net...
> Can someone familiar with Access 2003 please answer this question? I
> am asking because I don't have the use of A2003. When Access 2003
> finds an Access 2000 database, does it come up with some sort of
> question/suggestion indicating that you can convert this datbase into
> the new format? I am trying to trouble shoot a remote site where a
> big error message indicating the database was converted using the
> wrong method comes up when they try to open an Access 2000 database
> with either Access 2000 or Access 2002. AFAIK, there may be a small
> number of computers on-site using Acess 2003. Is it possible that
> someone has inadvertently converted the database into a format
> unreadable by earlier copies of Access?
>
> I thought of corruption, but this has happened to 2 different
> databases on the same site in less than 2 weeks! Co-incidence?
No. Wow, I'm impressed with all of that, it means little mind you, but it
makes me realise how little I know and how little I have learned. It is
giving me errors though. Does it go in the module behind the form, or does
it go into a real module in the Module area? I think I might have to sit
this one out Allen, it is just too advanced for my tiny brain I fear.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Did you copy the functions from the mvps.org links?
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... Firstly about this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I entered them as the source of two text boxes and it only returned me
#Name? What have I done wrong here - I am using Access 2000 - SP3.
_______________ _____________
Your post is very informative Allen. It seems to me that with each new
version of Office or Windows, Microsoft want to control things more
tightly. What they fail to realise (or dont care) is that the poor users
of their software are not all programmers or IT wizards, just normal joe
blow and Jane Citizen doing their everyday work. The registry change
needed to do automated mailmerge from Access to Word 2003 is a good
example. Sending people a registry patch with instructions on how to
apply it is not the easiest thing to achieve. Some of the people
involved do not even know what the registry is!
Again, thanks for your insightful reply.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... The A2000 MDE should be fine on Access 2002 and Access 2003. Further, it
cannot decompile, so it should not corrupt at the VBA level. Of course,
other kinds of corruption can still occur, such as those caused by Name
AutoCorrupt:
http://members.iinet.net.au/~allenbrowne/bug-03.html
Unless you are creating runtime installations, you should not have to
worry about the version of Windows on the users' machines. You do want
the know the user's version of Office, service pack, *and* JET service
pack. What we do is include a couple of text boxes on the form you use
for Help | About, like this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
The function calls are from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0054.htm
Completely different thought, but there is an incredibly stupid set of
dialog boxes the user can see in A2003 when they try to open a file. It
warns the user that the file may be unsafe to open and not to do it. If
they say, "Do it anyway", they are then presented with another dialog
warning that unsafe expressions are not blocked. It's quite a
complicated dialog with long messages and scrollbars, and it's hard to
even find the question you are answering, but again they have to go
against the Microsoft recommendation and choose the non-default answer.
Then they receive a *third* warning that they really should not do this!
And this happens every time they open the database! If Microsoft were
trying to destrory Access, they could hardly have come up with a more
effective strategy.
The A2003 user can avoid this recurring if they set their Macro Security
setting to Low, again something MS specifically recommends against.
Don't ask me why this garbage is in there, but could it be these dialogs
that are tripping up your users?
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net...
What about mde's Allen, obviously can't do this on-site with them.
But, surely if I decompile before I compile, the problem is less likely
to arise. This is the first time this has ever happened and it is twice
at the same site in 2 weeks. They use a mixture of 2000/XP/2003
(probably with a mixture of Service Packs applied too!) I could do
special versions for each program I guess, but it seems like a lot of
trouble. I know that A2003 can't produce an mde for 2002 or 2000, so I
guess that means I would need all 3 programs. Sorry, I am rambling.
Thinking out aloud.
Thanks for your help.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
> Access 2003 can use the A2000 database format without conversion.
> The question, "Do you want to Open or Convert?" occurs if you try to
> open an Access 97 in any version from 2000 onwards.
>
> Acess 2003 does use a different binary for the compiled code than
> A2000. This process is not perfect, so if you open the database in
> A2003 modify the forms/reports/module, save, and then open them in
> A2000 you can get corruption issues.
>
> For developers, the workaround is:
> 1. Decompile the database before, i.e. enter something like this at
> the command prompt while Access is not running. It is all one line,
> and include the quotes:
> "c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
> "c:\MyPath\MyDa tabase.mdb"
> 2. Compact.
> 3. Open in the other version, and Compile.
>
> For end users, you provide each workstation with its own local copy of
> the front end, compiled under the version not later than what they
> use. For example, create the MDE in Access 2000 and give copies to
> each user.
>
>
> "dixie" <di***@dogmail. com> wrote in message
> news:41******** @duster.adelaid e.on.net...
>> Can someone familiar with Access 2003 please answer this question? I
>> am asking because I don't have the use of A2003. When Access 2003
>> finds an Access 2000 database, does it come up with some sort of
>> question/suggestion indicating that you can convert this datbase into
>> the new format? I am trying to trouble shoot a remote site where a
>> big error message indicating the database was converted using the
>> wrong method comes up when they try to open an Access 2000 database
>> with either Access 2000 or Access 2002. AFAIK, there may be a small
>> number of computers on-site using Acess 2003. Is it possible that
>> someone has inadvertently converted the database into a format
>> unreadable by earlier copies of Access?
>>
>> I thought of corruption, but this has happened to 2 different
>> databases on the same site in less than 2 weeks! Co-incidence?
It should work if you just paste the code from each link into their own
modules, i.e. modules created from the Modules tab of the Database window
(not the module of the form).
API calls are a bit like that if you are not used to them. In reality, they
are just wrapper functions to pass a request to Windows for information, and
get an answer back.
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... No. Wow, I'm impressed with all of that, it means little mind you, but it
makes me realise how little I know and how little I have learned. It is
giving me errors though. Does it go in the module behind the form, or
does it go into a real module in the Module area? I think I might have to
sit this one out Allen, it is just too advanced for my tiny brain I fear.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Did you copy the functions from the mvps.org links?
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... Firstly about this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I entered them as the source of two text boxes and it only returned me
#Name? What have I done wrong here - I am using Access 2000 - SP3.
_______________ _____________
Your post is very informative Allen. It seems to me that with each new
version of Office or Windows, Microsoft want to control things more
tightly. What they fail to realise (or dont care) is that the poor users
of their software are not all programmers or IT wizards, just normal joe
blow and Jane Citizen doing their everyday work. The registry change
needed to do automated mailmerge from Access to Word 2003 is a good
example. Sending people a registry patch with instructions on how to
apply it is not the easiest thing to achieve. Some of the people
involved do not even know what the registry is!
Again, thanks for your insightful reply.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
The A2000 MDE should be fine on Access 2002 and Access 2003. Further,
it cannot decompile, so it should not corrupt at the VBA level. Of
course, other kinds of corruption can still occur, such as those caused
by Name AutoCorrupt:
http://members.iinet.net.au/~allenbrowne/bug-03.html
Unless you are creating runtime installations, you should not have to
worry about the version of Windows on the users' machines. You do want
the know the user's version of Office, service pack, *and* JET service
pack. What we do is include a couple of text boxes on the form you use
for Help | About, like this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
The function calls are from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0054.htm
Completely different thought, but there is an incredibly stupid set of
dialog boxes the user can see in A2003 when they try to open a file. It
warns the user that the file may be unsafe to open and not to do it. If
they say, "Do it anyway", they are then presented with another dialog
warning that unsafe expressions are not blocked. It's quite a
complicated dialog with long messages and scrollbars, and it's hard to
even find the question you are answering, but again they have to go
against the Microsoft recommendation and choose the non-default answer.
Then they receive a *third* warning that they really should not do
this! And this happens every time they open the database! If Microsoft
were trying to destrory Access, they could hardly have come up with a
more effective strategy.
The A2003 user can avoid this recurring if they set their Macro
Security setting to Low, again something MS specifically recommends
against. Don't ask me why this garbage is in there, but could it be
these dialogs that are tripping up your users?
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net...
> What about mde's Allen, obviously can't do this on-site with them.
> But, surely if I decompile before I compile, the problem is less
> likely to arise. This is the first time this has ever happened and it
> is twice at the same site in 2 weeks. They use a mixture of
> 2000/XP/2003 (probably with a mixture of Service Packs applied too!)
> I could do special versions for each program I guess, but it seems
> like a lot of trouble. I know that A2003 can't produce an mde for 2002
> or 2000, so I guess that means I would need all 3 programs. Sorry, I
> am rambling. Thinking out aloud.
>
> Thanks for your help.
>
> dixie
>
>
> "Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
> news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
>> Access 2003 can use the A2000 database format without conversion.
>> The question, "Do you want to Open or Convert?" occurs if you try to
>> open an Access 97 in any version from 2000 onwards.
>>
>> Acess 2003 does use a different binary for the compiled code than
>> A2000. This process is not perfect, so if you open the database in
>> A2003 modify the forms/reports/module, save, and then open them in
>> A2000 you can get corruption issues.
>>
>> For developers, the workaround is:
>> 1. Decompile the database before, i.e. enter something like this at
>> the command prompt while Access is not running. It is all one line,
>> and include the quotes:
>> "c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
>> "c:\MyPath\MyDa tabase.mdb"
>> 2. Compact.
>> 3. Open in the other version, and Compile.
>>
>> For end users, you provide each workstation with its own local copy
>> of the front end, compiled under the version not later than what they
>> use. For example, create the MDE in Access 2000 and give copies to
>> each user.
>>
>>
>> "dixie" <di***@dogmail. com> wrote in message
>> news:41******** @duster.adelaid e.on.net...
>>> Can someone familiar with Access 2003 please answer this question?
>>> I am asking because I don't have the use of A2003. When Access 2003
>>> finds an Access 2000 database, does it come up with some sort of
>>> question/suggestion indicating that you can convert this datbase
>>> into the new format? I am trying to trouble shoot a remote site
>>> where a big error message indicating the database was converted
>>> using the wrong method comes up when they try to open an Access 2000
>>> database with either Access 2000 or Access 2002. AFAIK, there may
>>> be a small number of computers on-site using Acess 2003. Is it
>>> possible that someone has inadvertently converted the database into
>>> a format unreadable by earlier copies of Access?
>>>
>>> I thought of corruption, but this has happened to 2 different
>>> databases on the same site in less than 2 weeks! Co-incidence?
OK, done that, I get a result from
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
but still get #Name? from the other one.
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I have both modules in place copied directly from the MVPS.org site.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... It should work if you just paste the code from each link into their own
modules, i.e. modules created from the Modules tab of the Database window
(not the module of the form).
API calls are a bit like that if you are not used to them. In reality,
they are just wrapper functions to pass a request to Windows for
information, and get an answer back.
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... No. Wow, I'm impressed with all of that, it means little mind you, but
it makes me realise how little I know and how little I have learned. It
is giving me errors though. Does it go in the module behind the form, or
does it go into a real module in the Module area? I think I might have
to sit this one out Allen, it is just too advanced for my tiny brain I
fear.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... Did you copy the functions from the mvps.org links?
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net...
Firstly about this:
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I entered them as the source of two text boxes and it only returned me
#Name? What have I done wrong here - I am using Access 2000 - SP3.
_______________ _____________
Your post is very informative Allen. It seems to me that with each new
version of Office or Windows, Microsoft want to control things more
tightly. What they fail to realise (or dont care) is that the poor
users of their software are not all programmers or IT wizards, just
normal joe blow and Jane Citizen doing their everyday work. The
registry change needed to do automated mailmerge from Access to Word
2003 is a good example. Sending people a registry patch with
instructions on how to apply it is not the easiest thing to achieve.
Some of the people involved do not even know what the registry is!
Again, thanks for your insightful reply.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
> The A2000 MDE should be fine on Access 2002 and Access 2003. Further,
> it cannot decompile, so it should not corrupt at the VBA level. Of
> course, other kinds of corruption can still occur, such as those
> caused by Name AutoCorrupt:
> http://members.iinet.net.au/~allenbrowne/bug-03.html
>
> Unless you are creating runtime installations, you should not have to
> worry about the version of Windows on the users' machines. You do want
> the know the user's version of Office, service pack, *and* JET service
> pack. What we do is include a couple of text boxes on the form you use
> for Help | About, like this:
> =fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
> =fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
> The function calls are from:
> http://www.mvps.org/access/api/api0065.htm
> http://www.mvps.org/access/api/api0054.htm
>
>
> Completely different thought, but there is an incredibly stupid set of
> dialog boxes the user can see in A2003 when they try to open a file.
> It warns the user that the file may be unsafe to open and not to do
> it. If they say, "Do it anyway", they are then presented with another
> dialog warning that unsafe expressions are not blocked. It's quite a
> complicated dialog with long messages and scrollbars, and it's hard to
> even find the question you are answering, but again they have to go
> against the Microsoft recommendation and choose the non-default
> answer. Then they receive a *third* warning that they really should
> not do this! And this happens every time they open the database! If
> Microsoft were trying to destrory Access, they could hardly have come
> up with a more effective strategy.
>
> The A2003 user can avoid this recurring if they set their Macro
> Security setting to Low, again something MS specifically recommends
> against. Don't ask me why this garbage is in there, but could it be
> these dialogs that are tripping up your users?
>
> "dixie" <di***@dogmail. com> wrote in message
> news:41******@d uster.adelaide. on.net...
>> What about mde's Allen, obviously can't do this on-site with them.
>> But, surely if I decompile before I compile, the problem is less
>> likely to arise. This is the first time this has ever happened and it
>> is twice at the same site in 2 weeks. They use a mixture of
>> 2000/XP/2003 (probably with a mixture of Service Packs applied too!)
>> I could do special versions for each program I guess, but it seems
>> like a lot of trouble. I know that A2003 can't produce an mde for
>> 2002 or 2000, so I guess that means I would need all 3 programs.
>> Sorry, I am rambling. Thinking out aloud.
>>
>> Thanks for your help.
>>
>> dixie
>>
>>
>> "Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
>> news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ...
>>> Access 2003 can use the A2000 database format without conversion.
>>> The question, "Do you want to Open or Convert?" occurs if you try to
>>> open an Access 97 in any version from 2000 onwards.
>>>
>>> Acess 2003 does use a different binary for the compiled code than
>>> A2000. This process is not perfect, so if you open the database in
>>> A2003 modify the forms/reports/module, save, and then open them in
>>> A2000 you can get corruption issues.
>>>
>>> For developers, the workaround is:
>>> 1. Decompile the database before, i.e. enter something like this at
>>> the command prompt while Access is not running. It is all one line,
>>> and include the quotes:
>>> "c:\Program Files\Microsoft office\office\m saccess.exe"
>>> /decompile
>>> "c:\MyPath\MyDa tabase.mdb"
>>> 2. Compact.
>>> 3. Open in the other version, and Compile.
>>>
>>> For end users, you provide each workstation with its own local copy
>>> of the front end, compiled under the version not later than what
>>> they use. For example, create the MDE in Access 2000 and give copies
>>> to each user.
>>>
>>>
>>> "dixie" <di***@dogmail. com> wrote in message
>>> news:41******** @duster.adelaid e.on.net...
>>>> Can someone familiar with Access 2003 please answer this question?
>>>> I am asking because I don't have the use of A2003. When Access
>>>> 2003 finds an Access 2000 database, does it come up with some sort
>>>> of question/suggestion indicating that you can convert this datbase
>>>> into the new format? I am trying to trouble shoot a remote site
>>>> where a big error message indicating the database was converted
>>>> using the wrong method comes up when they try to open an Access
>>>> 2000 database with either Access 2000 or Access 2002. AFAIK, there
>>>> may be a small number of computers on-site using Acess 2003. Is it
>>>> possible that someone has inadvertently converted the database into
>>>> a format unreadable by earlier copies of Access?
>>>>
>>>> I thought of corruption, but this has happened to 2 different
>>>> databases on the same site in less than 2 weeks! Co-incidence?
Open the Immediate Window (Ctrl+G).
Enter:
? fReturnSysDir()
On pressing Enter, you should get something like:
C:\WINDOWS\syst em32
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... OK, done that, I get a result from
=fGetProductVer sion(SysCmd(9) & "msaccess.e xe")
but still get #Name? from the other one.
=fGetProductVer sion(fReturnSys Dir() & "\msjet40.d ll")
I have both modules in place copied directly from the MVPS.org site.
dixie
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:41******** **************@ per-qv1-newsreader-01.iinet.net.au ... It should work if you just paste the code from each link into their own
modules, i.e. modules created from the Modules tab of the Database window
(not the module of the form).
API calls are a bit like that if you are not used to them. In reality,
they are just wrapper functions to pass a request to Windows for
information, and get an answer back.
--
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.
"dixie" <di***@dogmail. com> wrote in message
news:41******@d uster.adelaide. on.net... No. Wow, I'm impressed with all of that, it means little mind you, but
it makes me realise how little I know and how little I have learned. It
is giving me errors though. Does it go in the module behind the form,
or does it go into a real module in the Module area? I think I might
have to sit this one out Allen, it is just too advanced for my tiny
brain I fear.
dixie This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: TomT |
last post by:
We have a large application which has been in constant
change/development since Access 2.0. I've upgraded in the past to A95
(sorry I did that), then to A97, which has been fine, and stable. I
guess I'm what has been referred to as an Access 97 dinosaur....
I avoided A2000 due to issues I saw on ng's, but did install and play
around with the XP version, which seemed just fine.
I am finally about to take the plunge, and move the A97 app...
|
by: Tim Marshall |
last post by:
Subject simply does not work in A2003 for Netscape 7.x.
I googled and posted this before in the Fall. I saw a couple of ideas,
mostly to do with the registry which is an option, albeit a very
difficult one for some of my more illiterate users.
SendObject, at least on my PC, does not work properly with Netscape.
I am familiar with and have used Blat in Win 98 installations where my
app's opening "splash" form checks for the...
|
by: Paul Brady |
last post by:
I have A97 and A2K on my computer at home, on which I do volunteer
work for several databases on our county park system. One of the
clients uses A97, and the rest, A2K.
The A97 user is considering upgrading their Microsoft Office.
If they upgrade to Office 2000, I have no problems; I'll convert their
A97 database and we'll be in business.
But what if they upgrade to Office 2003 (I think there is such
a thing) and install A2003. Will I...
|
by: rdemyan via AccessMonster.com |
last post by:
With A2003, I'm having trouble accessing files in a folder on another
computer where back-end files, update files, etc are located. Here's the
scenario:
1) Computer #1 - A2003
2) Computer #2 - Access 2000; folder with back-ends for both computers and
'Update' folder.
I have a launcher program that launces my application (MyApp). The launcher
program also checks for updates to MyApp located in 'Update' folder (on
|
by: Salad |
last post by:
I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.
The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test
It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions in
http://support.microsoft.com/kb/824264/.
| | |
by: Zippy |
last post by:
I have recently moved from A97 to A2003.
I find it inconvenient that I can no longer double-click on the subform
to open it in full view. I had a hunt around the newgroups and couldn't
find anything helpful.
I know that I can right-click to open, but is there anything I can do to
make it do it the 'good old way'?
--
Zippy S
|
by: Salad |
last post by:
I have Microsoft Office Professional 2003 and the computer I connect to
also has A2003 retail. The others in that office use Access 2003 runtime.
Q1) I wanted to see if they were up-to-date on their service pack but
the "About Microsoft Office" menu item is missing when the run my app.
Is there a way to view the About form in the runtime version from the menu?
Q2) Also, do folks with a runtime version need the SP3 and hotfix?
Q3) ...
|
by: Wayne |
last post by:
I'm trying to overcome the problem that some users including myself
have noticed with combo boxes in A2003 databases that are run in
A2007. When the combo is tabbed out of the backstyle changes to
transparent. I haven't yet seen a fix for this.
If I design in A2003 now and then run the DB in A2007 in future the
combo box problem may arise. What I have thought of doing is
designing in A2007 and then compiling in A2003 for my current...
|
by: Samuel |
last post by:
My A2003 makes an Access 2000 file format by default. When I go to make
it a .mde I have to convert to A2003. That process looks to have been OK
and then when I select 'Make mde' Access hangs then fails.
How can I get access to make a 2003 file format from scratch?
With thanks to all,
Samuel
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
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 effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| | |
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, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
