I've run into problems with Access database as it's maximum size is limited to 2 GB. I've done a little research and found about split Access databases. When splitting the database, the original file remains and one new is added. I don't quite understand what I'll be getting with this. As I understand, the newly created file is a back-end - the data is stored here, the original file is just a front-end with forms, queries, etc. The limit on back-end file will still remain effective. Am I right? Perhaps multiple splits will do the trick, but I don't understand the concept of it.
我遇到了Access数据库的问题,因为它的最大大小限制为2 GB。我做了一些研究,发现了拆分Access数据库。拆分数据库时,原始文件将保留,并添加一个新文件。我不太明白我会得到什么。据我所知,新创建的文件是后端 - 数据存储在此处,原始文件只是表单,查询等的前端。后端文件的限制仍然有效。我对吗?也许多个分裂可以解决问题,但我不理解它的概念。
If multiple split is possible and I would be able to store more than 2 GB in virtually single database, how do I do it with OleDb. More specifically, am I supposed to interact with front-end database only, and Access will distribute the data by itself? I'm familiar with OleDb, just not sure about this whole split concept.
如果可以进行多次拆分,并且我可以在几乎单个数据库中存储超过2 GB,我该如何使用OleDb。更具体地说,我是否应该只与前端数据库进行交互,而Access会自行分发数据?我对OleDb很熟悉,对这整个拆分概念并不确定。
Thank you very much in advance.
非常感谢你提前。
1 个解决方案
#1
3
re: The limit on back-end file will still remain effective. Am I right? yes
re:后端文件的限制仍然有效。我对吗?是
Basically, you move all your table objects to one or more other databases and link to them in the front-end db with your forms, queries, etc.
基本上,您将所有表对象移动到一个或多个其他数据库,并使用表单,查询等在前端数据库中链接到它们。
One problem with splitting dbs is enforcing referential integrity. You can only do that within one .mdb file.
拆分dbs的一个问题是强制引用完整性。您只能在一个.mdb文件中执行此操作。
If you really need everyone to have access to massive amounts of data, consider storing it on SQL Server or some other back end instead.
如果您确实需要每个人都能访问大量数据,请考虑将其存储在SQL Server或其他后端。
#1
3
re: The limit on back-end file will still remain effective. Am I right? yes
re:后端文件的限制仍然有效。我对吗?是
Basically, you move all your table objects to one or more other databases and link to them in the front-end db with your forms, queries, etc.
基本上,您将所有表对象移动到一个或多个其他数据库,并使用表单,查询等在前端数据库中链接到它们。
One problem with splitting dbs is enforcing referential integrity. You can only do that within one .mdb file.
拆分dbs的一个问题是强制引用完整性。您只能在一个.mdb文件中执行此操作。
If you really need everyone to have access to massive amounts of data, consider storing it on SQL Server or some other back end instead.
如果您确实需要每个人都能访问大量数据,请考虑将其存储在SQL Server或其他后端。