Unfortunately, errors of this category tend to be the hardest to isolate because they don't come from commonly experienced problems and tend to be related to the environment where they occur only. Trouble-shooting is frequently a process of eliminating, step-by-step, one at a time, possible factors that impact, or could impact a relational database application. Have you tried repairing your installation of Office 365, or reinstalling it?Ĭan you create a new accdb and link to this table from it? And does that also leave out the same fields? Is this an on-premises instance of SQL Server, or a hosted instance? Have you relinked the tables (I assume yes, because you changed the UserID, but to be thorough.) When you say the fields are missing, does that mean there are no decimal fields at all, or that values in decimal fields are missing? ![]() That said, we can ask some clarifying questions that might help lead to insights.ĭid you recently install any updates to your Windows or Office? If so, when?ĭid this problem appear suddenly, i.e did it "work" in the past but no longer?ĭid you change any settings in your Access 365 application? In MS Access 2010 (actually 2007) you can create relationships between linked tables and local tables as well between linked and linked. ![]() Linked tables in Access use absolute paths rather than relative paths, so the development environment either has to have the same path as the production environment or a 'dynamic-linker' routine can be written in VBA. One of the difficulties of trouble-shooting problems like this is that there is no way for us to see the problem first-hand. Microsoft Access has two built-in utilities, Database Splitter and Linked Table Manager, to facilitate this architecture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |