Access 2003代码损坏问题 [英] Access 2003 code corruption problems
问题描述
我从97版开始就一直在使用Access，我已经迁移到了2003年。我已经注意到了很多奇怪的ActiveX / OLE和代码损坏的问题
编写数据库时出现
问题。我找到的唯一解决方案是
创建一个新数据库并从损坏的
文件中导入所有对象。
有没有其他人找到解决这个烦人问题的方法？我无法在微软的网站上找到任何有用的东西，而且我还没有看到关于这些问题的原因的任何
帖子。
任何信息都将不胜感激！
ja ********** @ gmail.com 写道：自97年以来我一直在使用Access我已经迁移到了2003年。
我在编写数据库时注意到了大量奇怪的ActiveX / OLE和代码损坏问题。我找到的唯一解决方案是创建一个新的数据库并从
损坏的文件中导入所有对象。
是否还有其他人找到解决这个烦人问题的方法？我无法在微软的网站上找到任何有用的东西，而且我还没有看到关于这些问题的原因的任何帖子。
任何信息都将不胜感激！
我发现如果我用A2003编辑一个A2000创建的ADP就会得到
损坏....
-
问候，
布拉德利
基督徒的回应
http://www.pastornet.net.au/response
我遇到了Access 2003的各种问题 - 现在我有一个奇怪的错误，它找不到一个名为''..'的宏。 。它似乎比之前版本的稳定性要低得多。而且我不知道
内部工作，但是代码/表单更改的保存似乎很有可能。
miss。
James Beswick< ja ********** @ gmail.com>写道：我遇到了Access 2003的各种问题 - 现在我有一个奇怪的错误，它找不到一个名为''..'的宏。它似乎比以前的版本稳定得多。我不知道它在内部工作，但代码/表单更改的保存似乎很有用。
想念。
我'没有令人信服的理由使用A2003，因为它仍然支持
A2000格式。
有很多东西虽然不起作用正如所料。
例如。根据我的经验，在A2000中运行良好但在A2003中没有运行的东西（使用完全相同的
2000格式数据库）...
ADP中的TransferText返回错误像Jet无法找到表格
dbo__tblMyTable。它似乎没有正确解释所有者/表
。如果您只使用表名，它将起作用，但如果您不是所有者，它将创建第二个同名表
属于当前用户。在A2000它工作正常。 （我基本上是使用ADP构建我自己的文本文件导入例程。从理论上讲，你需要将b $ b直接导入到SQL服务器中，但并不总是如此
对用户来说很实用。）
表单条件格式化没有按预期工作，似乎没有
更新直到记录失去焦点/更新。
我有一个有一个按钮调用另一个表单的表单。在A2000中它的作用是
，但是在A2003中它崩溃了。如果我从一个菜单项中调用它，那么
可以工作。
还有许多其他的怪癖。我无法回想起.....
当然在A2003中编辑A2000会导致数据库损坏。
''ol一般的经验法则是跳过
Access的每一个版本..但我认为不再适用了:)。很多人跳过了a
A2002 ....许多人仍然使用A2000。我怀疑A2005 / 6会提供多少但是我们
可以希望它更稳定，性能更好并且有更好的
表单设计功能。
-
问候，
布拉德利
基督徒的回应
http://www.pastornet.net.au/response
I''ve been using Access since version 97 and I''ve migrated to 2003. I''ve
noticed a substantial number of strange ActiveX/OLE and code corruption
problems when writing databases. The only solution I''ve found is to
create a new database and import all the objects from the corrupted
file.
Has anyone else found a solution to this annoying problem? I cannot
find anything useful on Microsoft''s website and I haven''t seen any
posts about the cause of these issues.
Any information would be greatly appreciated!
ja**********@gmail.com wrote:I''ve been using Access since version 97 and I''ve migrated to 2003.
I''ve noticed a substantial number of strange ActiveX/OLE and code
corruption problems when writing databases. The only solution I''ve
found is to create a new database and import all the objects from the
corrupted file.
Has anyone else found a solution to this annoying problem? I cannot
find anything useful on Microsoft''s website and I haven''t seen any
posts about the cause of these issues.
Any information would be greatly appreciated!
I''ve found if I edit a A2000 created ADP with A2003 it gets
corrupted....
--
regards,
Bradley
A Christian Response
http://www.pastornet.net.au/response
I''m running into all sorts of problems with Access 2003 - now I have a
weird error where it cannot find a macro called ''..''. It seems to be
remarkably less stable that the previous versions. And I don''t know it
works internally, but the saving of code/form changes seems hit and
miss.
James Beswick <ja**********@gmail.com> wrote:I''m running into all sorts of problems with Access 2003 - now I have a
weird error where it cannot find a macro called ''..''. It seems to be
remarkably less stable that the previous versions. And I don''t know it
works internally, but the saving of code/form changes seems hit and
miss.
I''ve found no compelling reason to use A2003 since it still supports the
A2000 format.
There are quite a few things though that don''t work as expected.
eg. Things that worked fine in A2000 but not in A2003 (using exact same
2000 format database) in my experience...
TransferText in an ADP returns an error like "Jet can''t find table
dbo__tblMyTable". It doesn''t seem to interpret the owner/table
correctly. If you use just the table name by itself it will work but if
you are not the owner it will create a second table of the same name
belonging to the current user. In A2000 it works fine. (I''ve basically
build my own text file importing routines when using ADPs. In theory you
should be importing into SQL server directly but it''s not always
practical for users).
Form Conditional Formatting doesn''t work as expected and seems to not
update until record looses focus/updates.
I''ve got a form that has a button that calls up another form. It works
in A2000, but in A2003 it crashes. If I call it from a menu item it
works though.
There are a number of other "quirks" I can''t recall offhand.....
And of course editing an A2000 in A2003 causes the database to become
corrupted.
The ''ol general rule of thumb is to skip every second version of
Access.. but I don''t think that works anymore:). Many people skipped
A2002.... many still use A2000. I doubt A2005/6 will offer much but we
can hope it''s more stable, has better performance and has some better
form design features.
--
regards,
Bradley
A Christian Response
http://www.pastornet.net.au/response
这篇关于Access 2003代码损坏问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
