Access 2007 Runtime Problems

[tokoloshi]

I would like to start a single thread that lists all of the problems associated to the use of Access Runtime here. If there are more than say 3 or 4 responses on a given problem it warrants a new thread with links from this central thread.

I have already noticed several discussions across the internet related to the topic, but there is no single source to go to for a listing of the common problems as experienced by developers.

I will kick off with the first of my problems as the first response, but this particular topic should act as a decent overview of the purpose of all problems/discussions listed under the broad heading of ACCESS 2007 RUNTIME ISSUES.

 

[tokoloshi]

Subform fails to display

This is a wierd one.

ENVIRONMENT
Data: Stored in SQL Server 2005, normalized to 3NF.
Link Method: Normal - linked tables from SQL into Access
Access File Type: ACCDB
Development Environment: Mix of XP & Vista
Client Environment: XP workstations, Windows 2003 Server with Active Directory installed for authentication and user account management.

Application
This is an application that links multiple tables in SQL Server into an interface in Access. A central form is used to maintain session, current client and current user information. Other forms look to this central form for information to filter out data to be presented.

Problem
One of the Master-Details forms in the application does not display the details subform when run from some of the workstations.

What is particularly strange is that the same form will display perfectly on some machines while incorrectly on others.

I have eliminated the user account and security aspects by logging in as the same user (administrator) on all machines.

I have installed the Access Developer Extensions on the development machines and generated an installer program from both an XP and a VISTA development machine and then reinstalled the application at the workstation level - to no avail.

I then redesigned the solution so that the sub-form was opened on its own, without any links to the master form.

Interestingly, I then receive a 2950 error. It also complains of an ODBC related problem.

I went into the ODBC manager on the troublesome XP machine and confirmed that the ODBC dsn file exists and that it can successfully connect. There are no problems there.

In fact, ALL other forms that have similar Master/Details forms work perfectly, which is what led me to creating the standalone form in the first place.

This is obviously not user, workstation, or form design related.

I am troubleshooting the SQL Server constraints now to see if I may have done something there, but I am beginning to get frustrated enough to take time out to document the problem and would like to know if anyone else has had a similar experience.

The problem seems to definitely point to the RunTime version, but I am reluctant to install the full version on a client machine to test that theory to the full without someone else confirming my suspicion that it probably is RunTime specific.

I will update this post with any new findings.