At work, users are in these days getting Office 2007 rolled out. Especially Access 2007, though, is causing trouble for a lot of users. Unfortunately, everything for me personally, and that makes it hard to pinpoint the error(s).
So, we have certain databases that many users use. Some forms in thoses databases has some calculated fields. When one of these forms are opened, the field doesn't display the calculated value. The status bar simple says "Calculating..." and that keeps on forever. However, if the user quickly switch/tab over over to one of certain other programs and back, the value has been calculated and everything is good. Programs that can be used to tab over to include Excel and Lotus Notes, but not MS Paint.
It seems more like a general Access-problem, than an 'error' in the forms (besides, the forms the pretty simple, most of them). The reason I mean that, is that we can reproduce a somewhat similar 'error' very easy and with VBA, queries or anything:
We launch Access 2007, create a new Black Database (2007/.accdb format). Access automatically opens the creation of a new table (Table1), we simple save it. Then, to the left in the Navigation Pane, we right click Table1, click Copy and then Paste it again in the Navigation....NOTHING SHOWS UP. Still only Table1. Once we tab over to for instance Excel and back to Access, the Navigation Pane shows both Table1 and it's copy. Same story when opening a database not maximized within Access 2007 (which is maximized itself). Now, when we maximize the database and does that but doesn't show the Close Database (X) button just below the Access Close button.
So it seems Access doesn't update it's current state in some way. There are more ways that comes to be seen. Like when in a Query (Datasheet View) and then clicking Design View. It then doesn't update the ribbon, making all the new buttons active. They are grayed outuntil we tab out and in again or in some other way 'refresh the view'.
As mentioned, everything works perfectly on my own computer, making this more of a mystery. It's nothing in our Active Directory/Group Policy, since I can log in on one of their computers and the problem will be there.
ANY suggentions are appreciated. It is a serious problem considering the amount of users and databases we have.
So, we have certain databases that many users use. Some forms in thoses databases has some calculated fields. When one of these forms are opened, the field doesn't display the calculated value. The status bar simple says "Calculating..." and that keeps on forever. However, if the user quickly switch/tab over over to one of certain other programs and back, the value has been calculated and everything is good. Programs that can be used to tab over to include Excel and Lotus Notes, but not MS Paint.
It seems more like a general Access-problem, than an 'error' in the forms (besides, the forms the pretty simple, most of them). The reason I mean that, is that we can reproduce a somewhat similar 'error' very easy and with VBA, queries or anything:
We launch Access 2007, create a new Black Database (2007/.accdb format). Access automatically opens the creation of a new table (Table1), we simple save it. Then, to the left in the Navigation Pane, we right click Table1, click Copy and then Paste it again in the Navigation....NOTHING SHOWS UP. Still only Table1. Once we tab over to for instance Excel and back to Access, the Navigation Pane shows both Table1 and it's copy. Same story when opening a database not maximized within Access 2007 (which is maximized itself). Now, when we maximize the database and does that but doesn't show the Close Database (X) button just below the Access Close button.
So it seems Access doesn't update it's current state in some way. There are more ways that comes to be seen. Like when in a Query (Datasheet View) and then clicking Design View. It then doesn't update the ribbon, making all the new buttons active. They are grayed outuntil we tab out and in again or in some other way 'refresh the view'.
As mentioned, everything works perfectly on my own computer, making this more of a mystery. It's nothing in our Active Directory/Group Policy, since I can log in on one of their computers and the problem will be there.
ANY suggentions are appreciated. It is a serious problem considering the amount of users and databases we have.