We found potential problems running Access 2010 applications in Distributed File System (DFS) environment and would like some help/suggestions.
We have large number of Access 2010 database running on our network without problems; however, we will be moving all our back-ends to Distributed File System (DFS) environment soon. Using a test database I found a potentially huge problem with DFS which I can't resolve. I hope someone will be able to shed some light on encountered problem.
When we moved the back-end to DFS Environment we seem to have lost all 'visible' relationships on the front-end. We found that putting the back-end in the root DFS folder worked fine; however, as soon as we placed the back-end in the second level folder, or several levels down, we lose all visible relationships in the front-end view. All 'physical' relationships still exist in the back-end regardless whether I put the back-end in the fist-level or eight-level folder. I tested various scenarios and data integrity was preserved in all instances.
When I link the front-end to back-end tables stored in the first-level folder and check relationships using Database Tools, Relationships menu, graphical representation in Relationships (database schema) form and queries are visible and in correct representation but as soon as I link to back-end stored in the folder deeper than the fists level and check relationships using Database Tools, Relationships menu I lose all visible relationships and graphical representation drawn by Access; however, all constraints, primary keys and foreign keys still work as expected
And also when I create a new query and add linked tables...
I can't see any graphical representation of relationships for any added tables.
All constraints, primary keys and foreign keys still work as expected but the graphical representation just isn't visible and when I manually create relationship in the front-end I can only see one-to-one link representations; however, when I check SQL it shows the correct syntax (see sample below).
SELECT
FROM tblGrants INNER JOIN tblGrantSupervisors ON tblGrants.GrantID = tblGrantSupervisors.GrantID;
I even tried changing the folder security for myself to FULL Control but that didn't make any difference.
The whole thing will be very confusion when we have to design and maintain the database (create new queries, forms and/ or reports) and make sure relationships work.
I am not sure what's causing it to behave the way it is; whether something to do with the way our network guys set the DFS environment or whether there is a patch our network guys haven't installed or something else. I believe our system is up-to-date with all service packs installed but I can't be sure at this stage.
However; I do know that our network guys are very paranoid when it comes to security so maybe they added/removed some network settings which are interfering with the way Access links to back-ends.
Does anyone know whether our network guys need to apply specific setting with our DFS environment?
I hope someone can come up with a hint to help us resolve the problem.
NOTE: I created a word document and screen dumps which could better explain my dilemma. The zipped files is stored at http://www1.hnehealth.nsw.gov.au/hneph/problems/Access2010DFSEnvironmentProblems.zip
for download.
Once again thanks for any feedback.
I hope someone can come up with a hint to help us resolve the problem.
Thanks.
John
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (1) |
Tidak ada komentar:
Posting Komentar