Double Back End (2K/XP)

Topic

New Reply

I am setting up a system for recording graves and burials. There are two types of data. The day to day burials and records which include about 65000 records, and is quite large. There is also the static data, prices etc. Will I take a performance hit, if I link the front end to 2 back ends. One with the big table, and one with the more static data. I would like to do this in order that I can be emailed the smaller back end during development, without having to get the whole 25 MEg back end. Meaning there will be FE.MDB linked to BE1.MDB and BE2.MDB.
Thanks

Reply | Quote

Replies

As far as I’m aware you will not suffer performance wise. I had to link to many BE’s in one app I wrote for no significant performance issue.
Pat

Reply | Quote

thanks for the info

Reply | Quote

I forgot to mention that these BE databases were spread all over a network, as we were doing some timings on them for just that reason.
Pat

Reply | Quote

I don’t think you will have any performance issues. The only thing I would be careful of is an arbitrary separation of tables such that you lose the ability to enforce referential integrity between tables (you can’t maintain RI between tables in different databases).

Reply | Quote

does that mean that the relationship diagram and all the RI in the front end between the linked tables is irrelevant?

Reply | Quote

Those diagrams in the frontend aren’t irrelevant. They do show the relationships between tables. However, what is shows comes mostly from the backend. You can create relationships in the frontend between linked tables from separate backends, but you CAN’T enforce RI between these tables.

Reply | Quote

One thing to watch out for that CAN sap performance, particularly with linked databases and a network involved, is subdatasheets and Name AutoCorrect. Name Autocorrect has caused nothing but trouble in the two version of Access it has “graced”, so turn it off. Subdatasheets are resource hogs, and you have to turn them off in each table separately or run code (which can be found in the help files on here in the Lounge if you search on “Subdatasheets”) to turn it off in all tables. Make sure you turn it off in both front and back end databases as well.

Reply | Quote