We run Access 2010 on a MS Small Business Server over a Terminal server. I have written an extensive project in Access that looks after all of our operational functions within the company. Clients, Debtors, Matters, Financial transactions, Payments receipts etc, Trust and General Account reporting, Activity logs etc.
I run a Production version and a development version of the project.
When I log into the server and access the development version when at work I can compile and test and then move the new version of form, Query or report to the Production site and all is OK - I don't have any problems.
I have the address of both versions as trusted locations in the trust centre.
I do a lot of work at home (as we all do) I log in remotely to the terminal server to get access to my work desk top. When I make changes to any of the objects in the development area then move to the production area. If I go into the production version to test the changes - everything is fine.
When I get into work and log into the terminal server at my desk the object that I made changes to at home remotely will not work. No error message not a thing to tell me what's wrong. It just ignores the request to open a form or report etc.
To overcome the problem I have to open that same object in the production area at work make a minor change and save it and it will work.
I have researched the Trusted Sites info all over and really haven't come up with a solution.
When I login remotely I log into my desktop environment why doesn't the system recognise that as a trusted location.
Can anyone help - this is driving me crazy. Is there some little thing that I'm missing here.
Any help to over come this problem would be much appreciated
Atrium
I run a Production version and a development version of the project.
When I log into the server and access the development version when at work I can compile and test and then move the new version of form, Query or report to the Production site and all is OK - I don't have any problems.
I have the address of both versions as trusted locations in the trust centre.
I do a lot of work at home (as we all do) I log in remotely to the terminal server to get access to my work desk top. When I make changes to any of the objects in the development area then move to the production area. If I go into the production version to test the changes - everything is fine.
When I get into work and log into the terminal server at my desk the object that I made changes to at home remotely will not work. No error message not a thing to tell me what's wrong. It just ignores the request to open a form or report etc.
To overcome the problem I have to open that same object in the production area at work make a minor change and save it and it will work.
I have researched the Trusted Sites info all over and really haven't come up with a solution.
When I login remotely I log into my desktop environment why doesn't the system recognise that as a trusted location.
Can anyone help - this is driving me crazy. Is there some little thing that I'm missing here.
Any help to over come this problem would be much appreciated
Atrium