praxis1949，


欢迎来到字节！


我们最近我们在工作中也升级到了64位计算机/软件（由于验证了新系统/软件的安全性问题，***总是很慢）。新的64位机器问题很少。


您已经完成了我的建议，那就是将旧对象导入到一个新的空白数据库中。我建议你定期查看你所做的事情，找出不兼容问题的位置并根据需要修复它们。


我不建议保留旧的过时项目，只是因为它仍然有效。可能有一些有效性，但系统和软件不等人。他们将继续前进。


有趣的是，我的妻子曾经在办公室工作，其中 一个 员工（自Stona时代以来一直在办公室工作）。他使用WordPerfect - 因为他总是使用WordPerfect。尽管办公室早已迁移到MS Office，但他继续使用WordPerfect。他们不得不搜索为他的WordPerfect版本购买一个特殊的升级，因为他的版本已经过时了。然而，他永远不会与任何人分享任何文件，因为他们的格式不同，但它为他工作。当他从办公室退休时，他们失去了所有的历史记录，因为他们的格式是没有人可以使用的。


我相信64位范式将会在这里待一会儿我认为仅仅咬紧牙关就值得付出努力。并进行迁移。你的移民会有一些令人头疼的问题 - 我不会给它涂上糖衣。但是，从长远来看 ，我相信这是值得的。你将为你的应用程序提供一个更稳定，更兼容的平台。


希望这个hepps！

praxis1949,

Welcome to Bytes!

We recently did our upgrade to 64-bit machines/Software here at work, too (government is always slow, due to validating security issues with new systems/software). We had very few issues with the new 64 bit machines.

You have already done what I would have recommended, and that is to import your old objects into a new, blank DB. I would recommend running through as much of what you do on a regular basis to find out where the incompatibility issues are and fix those as needed.

I would not recommend maintaining an old outdated project, "just because it still works." There may be some validity in that, but systems and software wait for no man. They will continue to advance.

Anecdotally, my wife used to work in an office in which there was one employee (who had been in the office since the Stona Age). He used WordPerfect--becuase he always used WordPerfect. Even though the office had long-since migrated to MS Office, he continued to use WordPerfect. They had to search to purchase a special upgrade for his version of WordPerfect because his version was so outdated. However, he could never share any documents with anyone, because they were in a different format, but it "worked for him." When he retired from the office, they lost all the historical records, because they were in a format that no one could use.

I do believe that the 64-bit paradigm will be here to stay for a while. I do think it is worth the effort to simply "bite the bullet" and make the migration. There will be some headaches involved with your migration--I won''t sugar coat it. But, in the long run, I do believe it is worth it. You will have a more stable, more compatible platform for your applications.

Hope this hepps!

感谢您的回复。到目前为止只发现了一些小问题（参考文献没有检查，一些小的查询误译与PDF发布报告有些奇怪[以其中一种奇怪的Access方式解决]）奇怪的是，使用64位版本和32位表格作为后面结束（在BE - FE测试中）。后端是否也需要翻译成64位？


再次感谢。应该帮我解决问题。


John S

Thanks for the reply. So far found only minor issues (References not checked, some minor query mistranslations something weird with publishing reports in PDF [ resolved in one of those weird Access ways]) Oddly, using a 64 bit version with a 32 bit set of tables as a back end (in the BE - FE testing configeration). Does the back end need to be translated to 64 bit too?

Thanks again. Should help me unchicken myself.

John S

我不认为BE需要翻译成64位，但它不是一个坏主意。可能存在一些严重的问题（我经历过）与BE的版本不同于FE。

I don''t think the BE needs to be translated into 64-bit, but it wouldn''t be a bad idea. There can be some serious issues (that I have experienced) with BEs not being the same version as the FE.