客户端中的MS Access升级 [英] Ms Access upgrading in client place

问题描述

升级软件时如何保留MS Access数据库..

使用自定义安装程序还是我们有任何想法.

目前，我的软件正在使用.mdb文件.

在C#中升级软件时如何在ms Access数据库中保留客户端数据

谢谢
Vijay r

How to preserve MS Access database while upgrading the software..

using custom installer or do we have any idea.

Currently My software is using .mdb file.

How to preserve the client data in the ms access database while upgrading the software in the C#

Thanks
Vijay r

推荐答案

软件升级如何破坏您的数据?它不应该.您需要保持软件向后兼容.

您可以执行某些schema evolution，但是您需要通过在演化过程中仅执行增量步骤来保持架构向后兼容.就是这样，您不应从架构中删除任何内容，而只需添加.

如果要从要摆脱的某些实体迁移到某些新实体，则无论如何都不要删除旧实体.而是在代码中创建deprecation的某种机制.当您的用户开始一些新工作(很难说它可以根据您的信息，也许您没有烂东西)时，代码应该使用新的实体，但是如果用户查询在架构演变之前创建的某些东西，旧实体应继续工作.

根据您的极简信息，我只能说这些.

请参见 http://en.wikipedia.org/wiki/Schema_evolution [

How upgrading of the software can disrupt your data? It should not. You need to keep your software backward-compatible.

You can do perform some schema evolution, but you need to keep the schema backward-compatible by making only incremental steps in evolution. That''s it, you should not remove anything from schema, only add.

If you want to migrate from some entities you want to get rid of to some new entities, do not remove old ones anyway. Instead, in the code, create some mechanism of deprecation. When your user starts some new work (hard to say what it can be based on your information, maybe you don''t have suck thing), the code should use new entities, but if the user queries for something created before the schema evolution, old entities should keep working.

This is all I can say based on your rather minimalistic information.

See http://en.wikipedia.org/wiki/Schema_evolution[^].

—SA

这篇关于客户端中的MS Access升级的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！