Background
I work for a large organization which has thousands of MS Access applications floating around. I didn't write any of these - in fact, most of the original authors have long since left the company - but from time to time another Access app lands on my desk for support. I would soooo love to replace access with a different solution.
我为一个大型组织工作，该组织有数千个MS访问应用程序。我没有写过这些东西——事实上，大多数原创作者已经离开公司很久了——但时不时地，另一个Access应用会出现在我的办公桌上，以获得支持。我非常乐意用另一种解决方案取代访问。
Requirement
I know that there are several good alternatives for the database part of MS Access (the Jet database), such as SQLite, MySQL, VistaDB, etc.
我知道对于MS Access (Jet数据库)的数据库部分有几个很好的替代方案，如SQLite、MySQL、VistaDB等。
What I would like to know is: Is there anything that will replace the front end part of MS Access?
我想知道的是:有什么东西可以代替MS Access的前端部分吗?
I.e. Something which can be used to build forms, write simple scripts and queries, etc?
例如，可以用来构建表单、编写简单的脚本和查询等?
Why?
@BracC asked "why replace access?" - A fair question indeed.
I want to get rid of access because:
@BracC问道:“为什么要替换访问?”-这个问题问得好。我想取消访问权限，因为:
- it hides logic, leading to hard-to-support applications. Logic can be in lots of different places, none of which provide or encourage any structure:
- macros
- 宏
- modules
- 模块
- queries
- 查询
- forms
- 形式
- 它隐藏逻辑，导致难以支持的应用程序。逻辑可以存在于许多不同的地方，其中没有一个提供或鼓励任何结构:宏模块查询表单
- its very nature encourages users to create "little" applications which become "not so little applications". Then the user leaves and I have to support a bunch of spaghetti. I know that access isn't the only culprit, but it's the leader in my organisation, and I would love to get rid of it completely.
- 它的本质就是鼓励用户创建“小”应用程序，而不是“小”应用程序。然后用户离开，我必须支持一堆意大利面。我知道访问并不是唯一的原因，但它是我所在组织的领导者，我很想彻底摆脱它。
For extra credit
what I would really love to find is something which can read in an MDB file and output something like C# which replicates the functionality. (Or any language - not fussy).
我真正希望找到的是可以在MDB文件中读取并输出类似c#的东西，它可以复制功能。(或任何语言——不要大惊小怪)。
I hope this is all clear. If not, please post a comment and I'll re-write/add detail.
我希望这一切都是清楚的。如果没有，请发表评论，我将重写/添加细节。
Update
@GuinnessFan makes some points I find interesting. I have added my comments to discuss those points.
@GuinnessFan说了一些我觉得有趣的事情。我补充了我的评论来讨论这些观点。
What we have done since I asked the question:
自从我问了这个问题之后我们做了什么:
- Got users to give us a definitive list of access applications they use and need. (The understanding is that any MDB files not on the list can be deleted - hooray!).
- 让用户向我们提供他们使用和需要的访问应用程序的最终列表。(理解是任何不在列表上的MDB文件都可以删除- hooray!)
- Analysed the MDBs on the list, coming to the following conclusions:
- Most of the "applications" consist of a single hard-coded query or a single linked table.
- 大多数“应用程序”由单个硬编码查询或单个链接表组成。
- Many are a small number of queries with, perhaps, a date parameter or similar.
- 许多查询可能是带有日期参数或类似的查询。
- very few (if any) have any truly complex logic.
- 很少(如果有的话)有任何真正复杂的逻辑。
- 分析了列表中的mdb，得出以下结论:大多数“应用程序”由单个硬编码查询或单个链接表组成。许多查询可能是带有日期参数或类似的查询。很少(如果有的话)有任何真正复杂的逻辑。
- We are now working through the list, converting most of the apps to SSRS (SQL Server Reporting Services) packages.
- 我们现在正在研究这个列表，将大多数应用程序转换为SSRS (SQL Server Reporting Services)包。
- Anything which can't be replicated using SSRS will become a hand-crafted web application. However, there aren't many of these.
- 任何不能使用SSRS复制的东西都将成为手工制作的web应用程序。然而，这样的例子并不多。
May I say many thanks, to everybody who has given me helpful answers.
我向所有给我有用答案的人表示感谢。
11 个解决方案
#1
5
You could check out Oracle's Application Express. It's free and it's geared toward Access developers.
您可以查看Oracle的应用程序Express。它是免费的，面向访问开发人员。
It has a migration assistant as well that you run your Access database through, it proccesses the data and the forms, migrates everything to an Oracle Database (this works with the free database, Oracle XE, and comes install by default) and builds web forms for your Access database.
它还有一个迁移助手，您可以通过它运行访问数据库，它处理数据和表单，将所有内容迁移到Oracle数据库(它与免费数据库Oracle XE一起工作，并默认安装)，并为您的访问数据库构建web表单。
So in the end you'll have your Access databases on the web, your data in Oracle and somewhat nice web front end for extending them.
所以最终你会在web上有你的访问数据库，在Oracle中有你的数据还有一些不错的网络前端来扩展它们。
As far as Oracle goes, the tool isn't half bad. You can sign up for a free instance to play around with here.
就Oracle而言，这个工具还不错。您可以在这里注册一个免费实例。
Here's the document that explains how you migrate Access Databases.
下面的文档解释了如何迁移访问数据库。
#2
6
I switched the back-end on one application from MSacces to MSSQL a few years ago. Kept the front-end, because it worked well, and I didn't find anything as easy to use/modify.
几年前，我将一个应用程序的后端从MSacces切换到MSSQL。保持前端，因为它工作得很好，而且我没有发现任何容易使用/修改的东西。
I've never seen a MSAccess -> C# translator. However, you might be able to find a MSAccess to VB6 translator (their syntaxes are roughly similar), and from there there are VB6->VB.Net translators (and even VB.Net ->C# translators)
我从未见过MSAccess -> c#翻译。但是，您可能可以找到对VB6转换器的MSAccess(它们的语法大致相同)，并且从那里有VB6->VB。Net翻译者(甚至VB)。网- > c#翻译)
#3
5
So, other than personnal distaste, why replace the Access front-end? May be easy to do for some (simple) databases, but most Access apps in the real world have a lot of complexity.
那么，除了个人厌恶之外，为什么要更换访问前端呢?对于一些(简单的)数据库来说可能很容易做到，但是现实世界中的大多数访问应用程序都有很多复杂性。
Lots of reasons for upgrading the back-end, of course (scalability, performance, db corruption, user-locking). Access even has a built-in "upgrade wizard" tool that allows you to split the forms and logic from the data, and upgrade the data to MS SQL server. If you want, use this wizard to upgrade the back-end to SQL Express, then manually migrate to another db platform.
当然，升级后端有很多原因(可伸缩性、性能、数据库损坏、用户锁定)。Access甚至还有一个内置的“升级向导”工具，可以将表单和逻辑从数据中分离出来，并将数据升级到MS SQL server。如果需要，请使用此向导将后端升级到SQL Express，然后手动迁移到另一个db平台。
Hope this is not too far off-topic, but sometimes all you need to do with Access is:
希望这不是离题太远，但有时你需要做的就是:
-
Upgrade the back-end (as we've already discussed)
升级后端(我们已经讨论过)
-
Always make sure the front-ends are locked down (read-only)
始终确保前端被锁定(只读)
-
If necessary, create different front-ends for different user roles (as a form of security).
如果需要，为不同的用户角色创建不同的前端(作为一种安全形式)。
-
If possible, have the front-ends copied locally on each workstation, for performance reasons. You may need to have a network script to check for new versions of the front-end.
如果可能的话，为了性能的原因，让前端在每个工作站本地复制。您可能需要一个网络脚本来检查前端的新版本。
I don't have any direct experience with it, but I did find an Access to ASP.Net converter tool called "Access Whiz" at http://www.microtools.us/
我对它没有任何直接的经验，但我确实找到了一个ASP。Net转换器工具，在http://www.microtools.us/被称为“Access Whiz”
#4
5
We used an internal app based on MS Access as a frontend to a MySQL database. We ran into lots of problems, and eventually rewrote the whole app in CodeGear Delphi 2007 for Win32. This has been a great success, although the migration did cost quite a lot of effort (training/hiring a couple of Delphi programmers, buying some third-party tools). I can wholeheartedly recommend Delphi, though. And AFAIK, integration with a MS Access back-end is certainly possible --- I once wrote a Delphi app that does just that, and it only cost me a couple of days to get a feature-complete version!
我们使用了一个基于MS Access的内部应用作为MySQL数据库的前端。我们遇到了很多问题，最终在CodeGear Delphi 2007中为Win32重写了整个应用程序。这是一个巨大的成功，尽管迁移确实花费了大量的精力(培训/雇佣几个Delphi程序员，购买一些第三方工具)。不过，我完全可以推荐Delphi。而AFAIK，与MS Access后端集成当然是有可能的——我曾经写过一个Delphi应用程序，我只花了几天时间就得到了一个功能完备的版本!
I realize this is a full programming solution, so you'd definitely loose some of the ease-of-use of MS Access for building front-ends. Then again, you can put together a database application in Delphi in 10 minutes without writing too much code --- no kidding! And since the 2009 release, the language is slowly becoming more mainstream again...
我知道这是一个完整的编程解决方案，所以您肯定会失去一些用于构建前端的MS访问的易用性。然后，您可以在10分钟内在Delphi中构建一个数据库应用程序，而不必编写太多代码——这不是开玩笑!自从2009年发行以来，这种语言又慢慢地变得越来越主流……
#5
4
@BradC
@BradC
I don't recomment MicroTools. I worked for a company a while back where we had the same problem. Unless MicroTools has made significant improvements to their product, it spits out garbage last I checked.
我不推荐MicroTools。我以前在一家公司工作过，我们也遇到过同样的问题。除非微工具对他们的产品做了重大的改进，否则它会吐出我上次检查过的垃圾。
What we found was that pretty much any upgrade path will require significant amounts of coding changes. All these tools are good for is to maintain a similar GUI from the original application. Their code had no object structure, just a bunch of utility functions that were dumped on each page to simulate the way Access provides record navigation. If you have a large number of forms, pulling out their solution and implementing your own takes some work and a ton of find-and-replace operations.
我们发现，几乎任何升级路径都需要大量的编码更改。所有这些工具都适用于维护来自原始应用程序的类似GUI。它们的代码没有对象结构，只有一堆实用函数，它们被转储到每个页面上，以模拟访问提供记录导航的方式。如果您有大量的表单，那么提取它们的解决方案并实现您自己的解决方案需要一些工作和大量的查找和替换操作。
We were so disappointed with MicroTools performance that we started writing our own converter. We were pumping out better ASP.NET forms than they were after a week of coding.
我们对微工具的性能非常失望，于是开始编写自己的转换器。我们正在推出更好的ASP。一个星期的编码后的表格。
#6
3
You won't find an server-class engine that also has the desktop interface design tools attached. The big server engines all expect you to use something like C++, C#, Java, or PHP to build your interface.
您不会找到一个服务器级的引擎，它还附带了桌面界面设计工具。大型服务器引擎都希望您使用c++、c#、Java或PHP之类的东西来构建接口。
I, too, would love to see an upgrade tool for access that would spit out some basic C# forms and talks to an equivalent SQL Server database. It seems that would be a big money-maker for Microsoft because they could use it as a way to up-sell customers to a full SQL Server.
我也希望看到一个升级工具来访问，它可以生成一些基本的c#表单，并与等效的SQL Server数据库进行对话。对于微软来说，这似乎是一个巨大的赚钱机器，因为他们可以用它来将客户升级到一个完整的SQL Server。
IIRC, there might be a way to tell an Access front end to talk to a SQL Server, or change the tables used by an Access front end to really be linked tables into a SQL Server, or something like that, but I've never had to use the feature myself.
IIRC，可能有一种方法可以告诉访问前端与SQL服务器对话，或者更改访问前端使用的表，使之真正链接到SQL服务器，或者类似的东西，但是我自己从来没有使用过这个特性。
#7
3
I have a different perspective for you to consider. Your main issue is that it hides logic and there is data and applications scattered through the organization.
我有一个不同的观点供你考虑。您的主要问题是它隐藏了逻辑，并且数据和应用程序分散在整个组织中。
Unfortunately I don't know of a RAD (rapid application development) tool that is as easy as Access to create functional forms.
不幸的是，我不知道一个RAD(快速应用程序开发)工具能像创建功能表单那样简单。
However I would recommend that you focus more on the possibility of centeralizing your data and logic and still allow Access as a front end. I support a database product called Advantage Database Server which supports RI (refferential integrity) rules, stored procedures, triggers, etc. that can all be managed on a centeral server thus bringing all of the logic to you. These Access front-ends could then link to the data backend using ODBC or OLEDB. If you switched to a solution like this then later down the road you would have flexibility to write other applications such as .NET, PHP, JDBC, etc. that tie into the same data while phasing Access front-ends out.
但是，我建议您更多地关注将数据和逻辑置于中心的可能性，并且仍然允许访问作为前端。我支持一个名为Advantage database Server的数据库产品，该产品支持RI (refferential诚信)规则、存储过程、触发器等，这些都可以在中心服务器上进行管理，从而为您带来所有的逻辑。然后，这些访问前端可以使用ODBC或OLEDB链接到数据后端。如果您切换到这样的解决方案，那么以后您将可以灵活地编写其他应用程序，如. net、PHP、JDBC等，这些应用程序在逐步访问前端时与相同的数据绑定在一起。
A good start would be to stop new Access development unless they're using this sort of data backend.
一个好的开端是停止新的访问开发，除非他们使用这种数据后端。
#8
3
Out of the 1000's of Access files how many have you been asked to support? I'm guessing less than 100. Why rebuild an application that A) no one uses B) works fine just the way it is?
在1000个访问文件中，有多少需要您支持?我猜不到100。为什么要重新构建一个A)没有人使用B)的应用程序?
You need to begin a policy that it is an acceptable practice for a large organization to develop custom applications in a robust, scalable, reliable, yadda yadda yadda environment. Identify the Access applications you feel are critical or are being outgrown and just work on those.
您需要开始一个策略，即在健壮、可伸缩、可靠的yadda yadda环境中开发自定义应用程序是一种可接受的实践。识别你觉得重要的访问应用程序，或者正在被超越，只在那些方面工作。
Be prepared to handle the expectation of getting their quick and dirty little applications on a quick turnaround. You'll have to show them the benefits of your new apps.
准备好处理他们的快速和肮脏的小应用程序的期望。你必须向他们展示你的新应用的好处。
I think you just need to be a resident expert and teach these users how to improve their application or get your input from the beginning to start them off right. The requirements to convert all of these files would otherwise be overwhelming.
我认为你只需要成为一名常驻专家，教这些用户如何改进他们的应用程序，或者从一开始就得到你的输入。否则，转换所有这些文件的要求将是压倒性的。
#9
1
Microtools offers Access Whiz, a set of Access conversion tools. It consists of Access to ASP .NET (VB/C#) converters, Access to VB6 converter, Access to WinForms (VB .NET/C#) converters and Access to Crystal Reports converter. More information and trial demos can be found at http://www.microtools.us.
微工具提供了访问Whiz，一组访问转换工具。它包括对ASP . net (VB/ c#)转换器的访问、对VB6转换器的访问、对WinForms (VB . net / c#)转换器的访问以及对Crystal Reports转换器的访问。更多信息和试验演示可以在http://www.microtools.us找到。
#10
#11
0
Is there anything that will replace the front end part of MS Access?
有什么东西可以替代MS Access前端部分吗?
Maybe Kexi?
也许绍兴?
#1
5
You could check out Oracle's Application Express. It's free and it's geared toward Access developers.
您可以查看Oracle的应用程序Express。它是免费的，面向访问开发人员。
It has a migration assistant as well that you run your Access database through, it proccesses the data and the forms, migrates everything to an Oracle Database (this works with the free database, Oracle XE, and comes install by default) and builds web forms for your Access database.
它还有一个迁移助手，您可以通过它运行访问数据库，它处理数据和表单，将所有内容迁移到Oracle数据库(它与免费数据库Oracle XE一起工作，并默认安装)，并为您的访问数据库构建web表单。
So in the end you'll have your Access databases on the web, your data in Oracle and somewhat nice web front end for extending them.
所以最终你会在web上有你的访问数据库，在Oracle中有你的数据还有一些不错的网络前端来扩展它们。
As far as Oracle goes, the tool isn't half bad. You can sign up for a free instance to play around with here.
就Oracle而言，这个工具还不错。您可以在这里注册一个免费实例。
Here's the document that explains how you migrate Access Databases.
下面的文档解释了如何迁移访问数据库。
#2
6
I switched the back-end on one application from MSacces to MSSQL a few years ago. Kept the front-end, because it worked well, and I didn't find anything as easy to use/modify.
几年前，我将一个应用程序的后端从MSacces切换到MSSQL。保持前端，因为它工作得很好，而且我没有发现任何容易使用/修改的东西。
I've never seen a MSAccess -> C# translator. However, you might be able to find a MSAccess to VB6 translator (their syntaxes are roughly similar), and from there there are VB6->VB.Net translators (and even VB.Net ->C# translators)
我从未见过MSAccess -> c#翻译。但是，您可能可以找到对VB6转换器的MSAccess(它们的语法大致相同)，并且从那里有VB6->VB。Net翻译者(甚至VB)。网- > c#翻译)
#3
5
So, other than personnal distaste, why replace the Access front-end? May be easy to do for some (simple) databases, but most Access apps in the real world have a lot of complexity.
那么，除了个人厌恶之外，为什么要更换访问前端呢?对于一些(简单的)数据库来说可能很容易做到，但是现实世界中的大多数访问应用程序都有很多复杂性。
Lots of reasons for upgrading the back-end, of course (scalability, performance, db corruption, user-locking). Access even has a built-in "upgrade wizard" tool that allows you to split the forms and logic from the data, and upgrade the data to MS SQL server. If you want, use this wizard to upgrade the back-end to SQL Express, then manually migrate to another db platform.
当然，升级后端有很多原因(可伸缩性、性能、数据库损坏、用户锁定)。Access甚至还有一个内置的“升级向导”工具，可以将表单和逻辑从数据中分离出来，并将数据升级到MS SQL server。如果需要，请使用此向导将后端升级到SQL Express，然后手动迁移到另一个db平台。
Hope this is not too far off-topic, but sometimes all you need to do with Access is:
希望这不是离题太远，但有时你需要做的就是:
-
Upgrade the back-end (as we've already discussed)
升级后端(我们已经讨论过)
-
Always make sure the front-ends are locked down (read-only)
始终确保前端被锁定(只读)
-
If necessary, create different front-ends for different user roles (as a form of security).
如果需要，为不同的用户角色创建不同的前端(作为一种安全形式)。
-
If possible, have the front-ends copied locally on each workstation, for performance reasons. You may need to have a network script to check for new versions of the front-end.
如果可能的话，为了性能的原因，让前端在每个工作站本地复制。您可能需要一个网络脚本来检查前端的新版本。
I don't have any direct experience with it, but I did find an Access to ASP.Net converter tool called "Access Whiz" at http://www.microtools.us/
我对它没有任何直接的经验，但我确实找到了一个ASP。Net转换器工具，在http://www.microtools.us/被称为“Access Whiz”
#4
5
We used an internal app based on MS Access as a frontend to a MySQL database. We ran into lots of problems, and eventually rewrote the whole app in CodeGear Delphi 2007 for Win32. This has been a great success, although the migration did cost quite a lot of effort (training/hiring a couple of Delphi programmers, buying some third-party tools). I can wholeheartedly recommend Delphi, though. And AFAIK, integration with a MS Access back-end is certainly possible --- I once wrote a Delphi app that does just that, and it only cost me a couple of days to get a feature-complete version!
我们使用了一个基于MS Access的内部应用作为MySQL数据库的前端。我们遇到了很多问题，最终在CodeGear Delphi 2007中为Win32重写了整个应用程序。这是一个巨大的成功，尽管迁移确实花费了大量的精力(培训/雇佣几个Delphi程序员，购买一些第三方工具)。不过，我完全可以推荐Delphi。而AFAIK，与MS Access后端集成当然是有可能的——我曾经写过一个Delphi应用程序，我只花了几天时间就得到了一个功能完备的版本!
I realize this is a full programming solution, so you'd definitely loose some of the ease-of-use of MS Access for building front-ends. Then again, you can put together a database application in Delphi in 10 minutes without writing too much code --- no kidding! And since the 2009 release, the language is slowly becoming more mainstream again...
我知道这是一个完整的编程解决方案，所以您肯定会失去一些用于构建前端的MS访问的易用性。然后，您可以在10分钟内在Delphi中构建一个数据库应用程序，而不必编写太多代码——这不是开玩笑!自从2009年发行以来，这种语言又慢慢地变得越来越主流……
#5
4
@BradC
@BradC
I don't recomment MicroTools. I worked for a company a while back where we had the same problem. Unless MicroTools has made significant improvements to their product, it spits out garbage last I checked.
我不推荐MicroTools。我以前在一家公司工作过，我们也遇到过同样的问题。除非微工具对他们的产品做了重大的改进，否则它会吐出我上次检查过的垃圾。
What we found was that pretty much any upgrade path will require significant amounts of coding changes. All these tools are good for is to maintain a similar GUI from the original application. Their code had no object structure, just a bunch of utility functions that were dumped on each page to simulate the way Access provides record navigation. If you have a large number of forms, pulling out their solution and implementing your own takes some work and a ton of find-and-replace operations.
我们发现，几乎任何升级路径都需要大量的编码更改。所有这些工具都适用于维护来自原始应用程序的类似GUI。它们的代码没有对象结构，只有一堆实用函数，它们被转储到每个页面上，以模拟访问提供记录导航的方式。如果您有大量的表单，那么提取它们的解决方案并实现您自己的解决方案需要一些工作和大量的查找和替换操作。
We were so disappointed with MicroTools performance that we started writing our own converter. We were pumping out better ASP.NET forms than they were after a week of coding.
我们对微工具的性能非常失望，于是开始编写自己的转换器。我们正在推出更好的ASP。一个星期的编码后的表格。
#6
3
You won't find an server-class engine that also has the desktop interface design tools attached. The big server engines all expect you to use something like C++, C#, Java, or PHP to build your interface.
您不会找到一个服务器级的引擎，它还附带了桌面界面设计工具。大型服务器引擎都希望您使用c++、c#、Java或PHP之类的东西来构建接口。
I, too, would love to see an upgrade tool for access that would spit out some basic C# forms and talks to an equivalent SQL Server database. It seems that would be a big money-maker for Microsoft because they could use it as a way to up-sell customers to a full SQL Server.
我也希望看到一个升级工具来访问，它可以生成一些基本的c#表单，并与等效的SQL Server数据库进行对话。对于微软来说，这似乎是一个巨大的赚钱机器，因为他们可以用它来将客户升级到一个完整的SQL Server。
IIRC, there might be a way to tell an Access front end to talk to a SQL Server, or change the tables used by an Access front end to really be linked tables into a SQL Server, or something like that, but I've never had to use the feature myself.
IIRC，可能有一种方法可以告诉访问前端与SQL服务器对话，或者更改访问前端使用的表，使之真正链接到SQL服务器，或者类似的东西，但是我自己从来没有使用过这个特性。
#7
3
I have a different perspective for you to consider. Your main issue is that it hides logic and there is data and applications scattered through the organization.
我有一个不同的观点供你考虑。您的主要问题是它隐藏了逻辑，并且数据和应用程序分散在整个组织中。
Unfortunately I don't know of a RAD (rapid application development) tool that is as easy as Access to create functional forms.
不幸的是，我不知道一个RAD(快速应用程序开发)工具能像创建功能表单那样简单。
However I would recommend that you focus more on the possibility of centeralizing your data and logic and still allow Access as a front end. I support a database product called Advantage Database Server which supports RI (refferential integrity) rules, stored procedures, triggers, etc. that can all be managed on a centeral server thus bringing all of the logic to you. These Access front-ends could then link to the data backend using ODBC or OLEDB. If you switched to a solution like this then later down the road you would have flexibility to write other applications such as .NET, PHP, JDBC, etc. that tie into the same data while phasing Access front-ends out.
但是，我建议您更多地关注将数据和逻辑置于中心的可能性，并且仍然允许访问作为前端。我支持一个名为Advantage database Server的数据库产品，该产品支持RI (refferential诚信)规则、存储过程、触发器等，这些都可以在中心服务器上进行管理，从而为您带来所有的逻辑。然后，这些访问前端可以使用ODBC或OLEDB链接到数据后端。如果您切换到这样的解决方案，那么以后您将可以灵活地编写其他应用程序，如. net、PHP、JDBC等，这些应用程序在逐步访问前端时与相同的数据绑定在一起。
A good start would be to stop new Access development unless they're using this sort of data backend.
一个好的开端是停止新的访问开发，除非他们使用这种数据后端。
#8
3
Out of the 1000's of Access files how many have you been asked to support? I'm guessing less than 100. Why rebuild an application that A) no one uses B) works fine just the way it is?
在1000个访问文件中，有多少需要您支持?我猜不到100。为什么要重新构建一个A)没有人使用B)的应用程序?
You need to begin a policy that it is an acceptable practice for a large organization to develop custom applications in a robust, scalable, reliable, yadda yadda yadda environment. Identify the Access applications you feel are critical or are being outgrown and just work on those.
您需要开始一个策略，即在健壮、可伸缩、可靠的yadda yadda环境中开发自定义应用程序是一种可接受的实践。识别你觉得重要的访问应用程序，或者正在被超越，只在那些方面工作。
Be prepared to handle the expectation of getting their quick and dirty little applications on a quick turnaround. You'll have to show them the benefits of your new apps.
准备好处理他们的快速和肮脏的小应用程序的期望。你必须向他们展示你的新应用的好处。
I think you just need to be a resident expert and teach these users how to improve their application or get your input from the beginning to start them off right. The requirements to convert all of these files would otherwise be overwhelming.
我认为你只需要成为一名常驻专家，教这些用户如何改进他们的应用程序，或者从一开始就得到你的输入。否则，转换所有这些文件的要求将是压倒性的。
#9
1
Microtools offers Access Whiz, a set of Access conversion tools. It consists of Access to ASP .NET (VB/C#) converters, Access to VB6 converter, Access to WinForms (VB .NET/C#) converters and Access to Crystal Reports converter. More information and trial demos can be found at http://www.microtools.us.
微工具提供了访问Whiz，一组访问转换工具。它包括对ASP . net (VB/ c#)转换器的访问、对VB6转换器的访问、对WinForms (VB . net / c#)转换器的访问以及对Crystal Reports转换器的访问。更多信息和试验演示可以在http://www.microtools.us找到。
#10
1
You can also take a look at Firebird
你也可以看看火鸟
Here is the way to migrate (you need Delphi)
这里是迁移的方法(需要Delphi)
I also find this MDB2FDB
我还找到了这个MDB2FDB
#11
0
Is there anything that will replace the front end part of MS Access?
有什么东西可以替代MS Access前端部分吗?
Maybe Kexi?
也许绍兴?