After making changes to a backend, my frontend seems only able to access fields in a temp table ~TMPCLP532891
As you can probably guess from this question, I am an intermediate user of Access at best, so please be patient with me if I don't understand everything.
I am using Microsoft Access version for Office 365 MSO (16.0.11929.20586 - 64 bit). I have a back-end on a network share and a front-end on my local computer. I am attempting to make changes to a form in the front-end.
I added several tables to the back-end with lookups to a table that already existed (modified the existing table, tblDemog). I did this so I could add that information to the front-end.
I have a tabbed control and can add a page to the form in the front-end. When I attempt to add existing fields to the form, they only exist in a table called ~TMPCLP532891.
If I try to open the form with any of these fields from the temp table on it or in the form's SQL, it asks for a value for that field in ~TMPCLP532891.
What I tried so far:
Any help would be appreciated.
I am using Microsoft Access version for Office 365 MSO (16.0.11929.20586 - 64 bit). I have a back-end on a network share and a front-end on my local computer. I am attempting to make changes to a form in the front-end.
I added several tables to the back-end with lookups to a table that already existed (modified the existing table, tblDemog). I did this so I could add that information to the front-end.
I have a tabbed control and can add a page to the form in the front-end. When I attempt to add existing fields to the form, they only exist in a table called ~TMPCLP532891.
If I try to open the form with any of these fields from the temp table on it or in the form's SQL, it asks for a value for that field in ~TMPCLP532891.
What I tried so far:
- I tried opening the back-end database and everything look fine.
- I tried deleting all table links and reimporting the table from the backend as links
- I tried deleting all table links and reimporting the table from the backend as tables and then splitting the database again
- I tried waiting a day to see if it would get less cranky
Any help would be appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Access crashed doing the BE - I made a copy of the BE and that worked fine when I did the C&E.
finished both FE and BE (both copies) and have now relaunched the FE. I'm checking it now.
The temporary table is gone - thanks! To add the fields I want to the FE form I need to use show all tables and add from the table that it should be showing by default. If I leave it at showing only fields in the current record source, the new fields don't show up. Is that what I should be seeing, or is this odd behavior?
<<If I leave it at showing only fields in the current record source, the new fields don't show up. Is that what I should be seeing, or is this odd behavior?>>
um...what is the recordsource for the form, a table, or a query? For query, you would only see the fields selected even if new fields were added. You'd have to modify the query unless it had "all fields", which is not a great thing to do (you only want to pull the data that you need).
Jim.
um...what is the recordsource for the form, a table, or a query? For query, you would only see the fields selected even if new fields were added. You'd have to modify the query unless it had "all fields", which is not a great thing to do (you only want to pull the data that you need).
Jim.
Thanks again - it is a query and the lag I am seeing/experiencing must be it rebuilding the query when I add new fields not currently in the query.
Thomas,
I would strongly encourage you, when doing a C&R on your backend, to copy that file to your PC, do the C&R there, then copy it back to its network location. Over the years, I've found that this is much more reliable than attempting to do the C&R against a database that is on the file server.
your mileage may vary.
Dale
I would strongly encourage you, when doing a C&R on your backend, to copy that file to your PC, do the C&R there, then copy it back to its network location. Over the years, I've found that this is much more reliable than attempting to do the C&R against a database that is on the file server.
your mileage may vary.
Dale
I have found that indeed it seems to work better and faster to do it that way - thanks.
ASKER