Split Database - Using Tables in Front-End

[BDibz]

Hello,

I have split my database into front-end and back-end for distribution. However, since one of the tables is used for data entry on-the-fly (which admittedly is considered "bad practice" but is the most effective way for these users to interact with this data), I have this table present in the front-end database. These tables appear like so:


However, what I've just noticed, is that it seems that these tables are not writing changes to the back-end database. Are these basically just a copy of those tables that I've been appending/updating? Is there a way I can make sure that the tables do make changes to the back end, or should I just go ahead and leave this DB un-split, since I'm kind of using it that way anyway?

[orange]

Have you updated with LinkedTable Manager after making changes to tables?
You can develop on single database, but if you plan to distribute to many simultaneous users, you should split the database, then test thoroughly, and ensure tables are being updated as per requirements.

[BDibz]

These aren't actually Linked Tables. I'm not sure exactly how Access is handling them. It seems like these tables are all self-contained in the front end part and aren't even dependent on the back-end. Maybe I should just delete the old back-end and re-split this when I'm done developing it?

[orange]

If these aren't linked tables, then what are they? What is your back-end?

[BDibz]

The crazy thing is, I don't know. I split these a while ago, but then kept working on the front-end part of it, and now I'm not sure what their connection actually is. Is it possible that the tables in the front-end part are just independent entities copied from the back-end?

This pic shows the front-end on the left and the back-end on the right. Same tables, but they're not actually linked. So maybe I goofed something up along the way - I've been working on a few projects at the same time so it's completely slipped my mind what happened here

[isladogs]

The image shows objects that have been assigned into a custom group 'User Objects'.
Custom groups can contain any type of database object: table, query, form etc etc
The small arrow in the bottom left is how these are displayed as they are effectively shortcuts

Your 3 tables are all LOCAL - stored in the FE

Here is another example



In this screenshot, the last item is a linked table - it has the link arrow on the top left as well as the shortcut arrow

[BDibz]

Thanks ridders. I'm assuming that if they're all local, and I have no linked tables in my front-end, I'm safe to delete the old split back-end and just continue on with the front.

[isladogs]

Suggest you change the way your db objects are displayed by using Object Types instead
Then in Tables section DOUBLE check you have no linked tables

Another way of checking is to MOVE your BE to a different location which will break any links you currently have
Then check whether all parts of your db still work correctly

[June7]

I have several processes that use 'temp' tables to present manipulated data. Db is split and temp tables are in frontend. Other tables are links to backend.

Yes, continue in frontend but you will need to properly split and link before deployment. Each user should have own copy of frontend linked to common backend.

[BDibz]

Ridders, I went ahead and did those and turns out I was good to go, so just continuing with the front end.

Will have to be more careful down the line when I do split again to make sure things are properly linked and not just floating duplicates.

Thanks everyone

[isladogs]

OK glad you got it sorted ....