G
Guest
Access 2002 ADP & SQL 2005 Views
Recently we upgrade from Access 2002 ADP & SQL 2000, to Access 2002 ADP &
SQL2005.
This is cause a a few problems which we are trying to sovle.
Problem 1:
I a form which is based on a view for recordset, when I delete a record from
the form I get the message: "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 able to fix this by setting the "Unique Table" property of the form.
Although we didn't have to set this property when we were using SQL2000
So far so good. When I try to insert a new record I get this message: "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 tried to fix this problem by setting the "Resync Command" property.
When I set this property to something (anything! even just a single
character) then the message isnt't displayed and the record is saved and
displayed properly - but with one exception. The primary key, which is also
autonumber is always displayed as 0. Although after I close and open the
form, the data appears that was written fine.
The only way I was able to fix this was by changing the data source of the
form, from a View, to a hard coded SQL statement identical to the View.
In this case the form works fine, and the autonumber primary key is always
displayed properly.
Any suggestions? It is very strange to me as to why the"Resync Command"
works by just putting anything inside it. But even then how can I make the
primary key autonumber field appear properly?
Prolem 2:
Something is definately wrong with sorting.
When I open a form which is based on a view for recordset, the sorting order
of the form is completely different from the sorting order of the view.
Again the only I was able to fix this was by changing the data source of the
form, from a View, to a hard coded SQL statement identical to the View.
What is happening here ? The solution is the same as in problem 1!?? Could
it be that Access has trouble dealing with SQL 2005 views? What can I do to
make the sort work with setting the data source to a hard coded statement?
Recently we upgrade from Access 2002 ADP & SQL 2000, to Access 2002 ADP &
SQL2005.
This is cause a a few problems which we are trying to sovle.
Problem 1:
I a form which is based on a view for recordset, when I delete a record from
the form I get the message: "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 able to fix this by setting the "Unique Table" property of the form.
Although we didn't have to set this property when we were using SQL2000
So far so good. When I try to insert a new record I get this message: "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 tried to fix this problem by setting the "Resync Command" property.
When I set this property to something (anything! even just a single
character) then the message isnt't displayed and the record is saved and
displayed properly - but with one exception. The primary key, which is also
autonumber is always displayed as 0. Although after I close and open the
form, the data appears that was written fine.
The only way I was able to fix this was by changing the data source of the
form, from a View, to a hard coded SQL statement identical to the View.
In this case the form works fine, and the autonumber primary key is always
displayed properly.
Any suggestions? It is very strange to me as to why the"Resync Command"
works by just putting anything inside it. But even then how can I make the
primary key autonumber field appear properly?
Prolem 2:
Something is definately wrong with sorting.
When I open a form which is based on a view for recordset, the sorting order
of the form is completely different from the sorting order of the view.
Again the only I was able to fix this was by changing the data source of the
form, from a View, to a hard coded SQL statement identical to the View.
What is happening here ? The solution is the same as in problem 1!?? Could
it be that Access has trouble dealing with SQL 2005 views? What can I do to
make the sort work with setting the data source to a hard coded statement?