first_page the funky knowledge base
personal notes from way, _way_ back and maybe today

Access 2000/2002/XP Forms: The Importance of the UniqueTable Property; ResyncCommand

This was the error message that started it all: "The data was added to the database but the data won't be displayed in the form because it doesn't satisfy the criteria in the underlying record source." I was getting this error when I set the RecordSource property of an Access Data Project Form to the name of a SQL Server view that contained joins.

This problem is similar to the problem resolved by KB article 248095 ("ACC2000: Error When You Add Record to a Form That Is Based on a Stored Procedure") which leans heavily toward rolling one's own ResyncCommand string.

Before resorting this, I recommend setting the UniqueTable property of the form to see if Access can create a ResyncCommand string for you. Entering the name of one table is far less work than trying to create a ResyncCommand value.

For more philosophy, the details can be found at MSDN, the article "Chapter 3: Building Microsoft Access 2000 Client/Server Applications" at:

http://msdn.microsoft.com/library/en-us/dnapg/html/apg03.asp
mod date: 2003-06-11T00:18:41.000Z