Re-occurring problem opening Access 2003 DB in Windows Expl.

I had this problem previously while evaluating Version 6, Build 419, and after speaking with tech support at 2X, the problem was resolved by upgrading the Microsoft RDP client to Version 6 and de-selecting "local disk drives" in the Farm Properties -Local Resources tab on the client.
We have purchased the software, all version 6 and now build 421, and we are experiencing this problem once again.

The problem:

When I use Windows Explorer as a Published App, go to a directory where the Access 2003 database is located and attempt to open it, I get the following message:
"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access this item."
I can open all other files e.g., Excel, Word, .pdf, etc...through Explorer, just not Access 2003 databases.

When in Access 2003 as a Published App, I have no problem opening any databases.

More succinctly, the app works in the following scenarios:
Through a regular RDP session to the server (bypassing 2X), in Windows Explorer, clicking on and opening Access database works.

Through a 2X published "Desktop" , then opening Windows Explorer in the session, clicking on and opening Access database works.

Through a 2X published "Access 2K3" app, clicking on and opening Access database works.

Through 2X published "Windows Explorer" app, attempt to open an Access database does not work.....results in the error message described previously.

Oddly enough, the problem was resolved briefly yesterday after I set the display properties in the Local Resources of the client to High Color (16 bit) to match the display on the terminal servers after noticing a color problem in the sessions.....I could then open an Access 2003 database fro the MS Windows Explorer published app for a while...................but the problem re-occurred this morning.....I have no clue at this point what's going on......any help would be greatly appreciated.

 

Did you check Event Viewer for any errors or warning there?
Did you try publishing Acess with this file set as a parameter?

 

I will check the event viewer...
And I'm not quite sure what you mean by using Access with this file set.....

 

Interestingly enough, I have the same symptoms here, but with an application and under v5.1 build 315. It's been going on for many months now, but I've been able to work around it until now.

The application can be run from an RDP Remote Desktop session or via a 2x Remote Desktop connection. It also does not occur for some users... however, it does for my account, which is has Domain Admin rights.

The application is run from a network share... but if I make a local copy on the Terminal Server, it will run; but the user's logon script etc will not be invoked. (And without certain other network resources, it's a bit useless.)

The previous scenarios in terms of when the conditions do and do not occur also hold true here... there's nothing in the event log that applies, running procmon hasn't turned anything up and the 2x log has very little information besides performance status and user application lists.

Any ideas?

Cheers,

Jo-jo.