We have started encountering a VERY strange problem on our Terminal Services 2008 server.
Our Access 2010 Applications run fine for about 4 weeks, and then all of a sudden calculated fields stop displaying their values on forms. If we reboot the server without changing anything at all, the applications all start to work again without issue.
Today the issue is larger than before. Apart from the usual issue mentioned above, Rowsource queries for combo-boxes, forms, subforms, listboxes etc. have stopped returning data when they run against a backend database table that is in an Access (JET) database!
If you execute the query yourself in Query Designer, data is returned, but through the application the exact same query returns no data.
Queries that run against SQL Server tables return data without issue.
We know that if we reboot the server the issue will go away, so it seems to be a resource issue of some kind that builds up over time.
Has anyone else ever encountered anything remotely like this, or have any ideas what may be causing the issues??
It looks like it is an issue with the JET Engine somehow because accessing data through ODBC to SQL Server works fine.
We have stopped and started the Windows Indexing service and freed up the memory and disk space it was hogging, but that has made no difference.
We never had these issues with Access 2003, and they have only started with Access 2010.