[AccessD] Write Conflict SQL and adp

Eureka!

I was stumbling around with Arthur's suggestion about views and 
filters and came up with an error to the effect that you can't change 
a timestamp field.  It had been included in the SELECT 
dbo.tblLAWSDensity.* part of the view.  So I changed the sproc to 
list all the fields individually except for the timestamp and it 
worked.  I now have filtering on the server side.

This now makes sense because (I am guessing here) as the timestamp 
field was included in the sproc, it was being updated whenever a new 
record was being sent back to the server, therefore not matching with 
the old value of the timestamp.

Thanks everyone for your input.

David


At 24/06/2009, you wrote:
>Ah, I couldn't see how I could pass the location parameter to the
>view but filtering would work for small tables.
>
>In one case there are several thousand records and growing each
>month.  If possible I would prefer this to be filtered at the SQL end
>rather than the Access end.
>
>I will test it out anyway.  Thanks.
>
>David
>
>At 24/06/2009, you wrote:
> >I return to my former suggestion: create a view which does the same thing as
> >your sproc, and run that instead. Thanks to Access's filtering ability, you
> >can easily scope this to the particular record(s) you want
> >One proviso, which is sure you get you into trouble: if your subform(s)
> >depend on a query that involves the parent table, lose the parent-table
> >link. Else you are guaranteed to get into trouble.
> >
> >A.
> >--
> >AccessD mailing list
> >AccessD at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/accessd
> >Website: http://www.databaseadvisors.com
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com