A2003 - 转换选项 [英] A2003 - option to convert

问题描述

熟悉Access 2003的人可以回答这个问题吗？我问b $ b因为我没有使用A2003。当Access 2003找到一个

Access 2000数据库时，它是否会提出某种问题/建议

表示您可以将此数据库转换为新格式？我是

试图麻烦拍摄一个远程网站，其中一个大错误消息表示数据库使用错误的方法转换为
，当他们尝试

使用Access 2000或Access 2002打开Access 2000数据库.AFAIK，

使用Acess 2003可能会有少量现场计算机。是

可能是某人无意中将数据库转换为以前的Access副本无法读取的格式？


我想到了腐败，但这已经发生在2

不同的数据库在不到两周的时间内在同一个网站上！共同发生？


dixie

解决方案

Access 2003可以使用A2000数据库格式而无需转换。

问题，你想打开还是转换？如果你尝试在2000年以后的任何版本中打开一个

Access 97，就会发生这种情况。

Acess 2003确实对编译后的代码使用了不同的二进制文件而不是A2000。

这个过程并不完美，所以如果你在A2003中打开数据库修改

表格/报告/模块，保存，然后在A2000中打开它们即可获得< br $>
腐败问题。


对于开发人员来说，解决方法是：

1.之前反编译数据库，即输入类似的内容Access未运行时

命令提示符。这是一行，并包括

引号：

" c：\Program Files \ Microsoft Office \ office \ msmscess.exe" / decompile

" c：\ MyPath \ MyDatabase.mdb"
2.紧凑。

3.在其他版本中打开和编译。


对于最终用户，您为每个工作站提供了自己的

前端的本地副本，在不迟于版本的情况下编译他们使用。对于

示例，在Access 2000中创建MDE并为每个用户提供副本。


-

Allen Browne - Microsoft MVP。西澳大利亚州珀斯。

访问用户提示 - http：// allenbrowne.com/tips.html

回复群组，而不是mvps dot org的allenbrowne。


" dixie" <二*** @ dogmail.com>在消息中写道

news：41 ******** @ duster.adelaide.on.net ...

熟悉Access 2003的人可以回答这个问题题？我问，因为我没有使用A2003。当Access 2003找到一个
Access 2000数据库时，它是否会提出某种问题/建议，表明您可以将此数据库转换为
新格式？我试图麻烦拍摄一个远程站点，其中一个大错误
消息指示数据库使用错误的方法转换
当他们尝试使用Access 2000打开Access 2000数据库时
或Access 2002.AFAIK，现场可能有少量计算机使用Acess 2003.是否有人可能无意中将数据库转换为Access早期副本无法读取的格式？ br />
我想到了腐败，但是在不到两周的时间里，在同一个网站上发生了2个不同的数据库！共同发生？

dixie

mde'的艾伦怎么样，显然不能在现场这样做跟他们。但是，

肯定如果我在编译之前反编译，问题就不太可能出现了。

这是第一次发生这种情况并且两次相同
2周内
网站。他们使用的是2000 / XP / 2003的混合物（可能还有应用的
混合服务包！）我想我可以为每个

程序做特殊版本，但是这似乎很麻烦。我知道A2003

不能产生2002年或2000年的mde，所以我想这意味着我需要

所有3个程序。对不起，我在散步。大声思考。


感谢您的帮助。


dixie

" Allen Browne" <铝********* @ SeeSig.Invalid>在留言中写道

news：41 ********************** @ per-qv1-newsreader-01.iinet.net.au ...

Access 2003可以使用A2000数据库格式而无需转换。
问题，您要打开还是转换？如果你尝试在2000年以后的任何版本中打开Access 97，就会发生这种情况。

Acess 2003确实使用了与A2000不同的编译代码二进制文件。
这个过程不是完美，所以如果你在A2003中打开数据库修改表单/报表/模块，保存，然后在A2000中打开它们就可以得到腐败问题。

对于开发人员，解决方法是：
1.之前反编译数据库，即在Access未运行时在
命令提示符下输入类似的内容。这是一行，并且包含引号：
" c：\Program Files \ Microsoft Office \ office \ msmscess.exe" / decompile
" c：\ MyPath \ MyDatabase.mdb"
2.紧凑。
3.在另一个版本中打开，然后编译。

对于最终用户，您为每个工作站提供了自己的
前端本地副本，在不迟于其使用的版本下编译。例如，在Access 2000中创建MDE并为每个用户提供副本。

- Allen Browne - Microsoft MVP。西澳大利亚州珀斯。
访问用户提示 - http://allenbrowne.com/ tips.html
回复群组，而不是mvps dot org的allenbrowne。

dixie <二*** @ dogmail.com>在消息中写道
新闻：41 ******** @ duster.adelaide.on.net ...

熟悉Access 2003的人能否回答这个问题？我问，因为我没有使用A2003。当Access 2003找到一个
Access 2000数据库时，它是否会提出某种问题/建议，表明您可以将此数据库转换为
新格式？我试图解决远程站点的问题，其中一个大错误
消息表明数据库是使用错误的方法转换的
当他们尝试使用Access打开Access 2000数据库时出现
2000或者Access 2002.AFAIK，可能会有少量的计算机在现场使用Acess 2003.是否有人可能无意中将数据库转换为早期副本<
访问？

我想到了腐败，但是在不到两周的时间里，在同一个网站上发生了2个不同的数据库！共同发生？

dixie

A2000 MDE在Access 2002和访问2003.此外，它
无法反编译，因此它不应该在VBA级别损坏。当然，

其他类型的腐败仍然可能发生，例如那些由名字造成的损失

AutoCorrupt：
http://members.iinet.net.au/~allenbrowne/bug-03.html


除非您正在创建运行时安装，否则您不必担心用户计算机上的Windows版本是否为
。您确实需要知道用户的Office，Service Pack，*和* JET服务包的版本

。我们

做的是在用于帮助|的表单上包含几个文本框关于，

是这样的：

= fGetProductVersion（SysCmd（9）&" msaccess.exe"）

= fGetProductVersion（fReturnSysDir（ ）&" \ msjet40.dll"）

函数调用来自： http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0054.htm

完全不同的想法，但是当用户在尝试打开文件时，可以在A2003中看到一组非常愚蠢的

对话框。它b / b
警告用户该文件可能不安全而无法打开。如果他们说无论如何，那么他们会看到另一个对话框警告

，表示不会阻止不安全的表达。这是一个非常复杂的对话框

有长信息和滚动条，甚至很难找到你正在回答的问题

，但他们又要这么做违反Microsoft

建议并选择非默认答案。然后他们收到了一个

*第三个警告他们真的不应该这样做！这种情况发生在他们打开数据库的每一个时间！如果微软试图破坏Access，那么他们几乎无法提出更有效的策略。


A2003用户可以避免这种情况再次发生他们的Macro Security

设置为Low，这也是MS专门建议的。不要
问我为什么这里有垃圾，但可能是这些对话框是否会哄骗你的用户？


-

Allen Browne - 微软MVP。西澳大利亚州珀斯。

访问用户提示 - http：// allenbrowne.com/tips.html

回复群组，而不是mvps dot org的allenbrowne。


" dixie" <二*** @ dogmail.com>在消息中写道

新闻：41 ****** @ duster.adelaide.on.net ...

mde'的艾伦怎么样，显然可以'不要和他们在现场这样做。但是，
肯定如果我在编译之前反编译，问题就不太可能出现了。这是第一次发生这种情况，在两周内在同一个网站上两次。他们使用的是2000 / XP / 2003的混合物（可能是应用了Service Packs的混合物！）我可以为每个程序做特殊的版本
，但是看起来很麻烦。我知道A2003不能生成2002年或2000年的mde，所以我猜这意味着我需要所有3个程序。对不起，我在散步。大声思考。

感谢您的帮助。

dixie

" Allen Browne" <铝********* @ SeeSig.Invalid>在消息中写道
新闻：41 ********************** @ per-qv1-newsreader-01.iinet.net.au ... < blockquote class =post_quotes> Access 2003可以使用A2000数据库格式而无需转换。
问题，你想打开还是转换？如果你尝试在2000年以后的任何版本中打开Access 97，就会发生这种情况。

Acess 2003确实使用了与A2000不同的编译代码二进制文件。
这个过程不是完美，所以如果你在A2003中打开数据库修改表单/报表/模块，保存，然后在A2000中打开它们就可以得到腐败问题。

对于开发人员，解决方法是：
1.之前反编译数据库，即在Access未运行时在
命令提示符下输入类似的内容。这是一行，并且包含引号：
" c：\Program Files \ Microsoft Office \ office \ msmscess.exe" / decompile
" c：\ MyPath \ MyDatabase.mdb"
2.紧凑。
3.在另一个版本中打开，然后编译。

对于最终用户，您为每个工作站提供了自己的前端本地副本，在不迟于其使用的版本下编译。
例如，在Access 2000中创建MDE并将副本提供给每个用户。

" dixie" <二*** @ dogmail.com>在消息中写道
新闻：41 ******** @ duster.adelaide.on.net ...

熟悉Access 2003的人能否回答这个问题？我问，因为我没有使用A2003。当Access 2003找到一个
Access 2000数据库时，是否会提出某种问题/建议，表明您可以将此数据库转换为新格式？我试图麻烦拍摄一个远程站点，当他们尝试使用Access 2000打开Access 2000数据库时出现一个大的
错误消息，表明数据库是使用错误的
方法转换的或Access 2002.AFAIK，使用Acess 2003可能会有少量现场计算机。是否有人可能无意中将数据库转换为早期版本无法读取的格式
副本访问？

我想到了腐败，但是在不到两周的时间里，在同一个网站上发生了2个不同的数据库！共同发生？

dixie

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

解决方案

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\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.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.adelaide.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*********@SeeSig.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\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.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.adelaide.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:
=fGetProductVersion(SysCmd(9) & "msaccess.exe")
=fGetProductVersion(fReturnSysDir() & "\msjet40.dll")
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******@duster.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*********@SeeSig.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\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.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.adelaide.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

这篇关于A2003 - 转换选项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！