Jim Dettman
jimdettman at verizon.net
Tue Jan 10 21:53:47 CST 2012
Glad it worked. A time stamp field isn't really a time stamp BTW, but activates row versioning in SQL. JET will use that if it exists to determine if a record has changed or not since it last visited it. Adding one is always a good idea. There is no real downside to it and it usually takes care of any record set issues. I've made it a habit to always stick one in every table. Jim Sent from my iPhone On Jan 10, 2012, at 10:31 PM, jwcolby <jwcolby at colbyconsulting.com> wrote: > Adding the timestamp field fixed the problem. > > Thanks Jim. > > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > On 1/10/2012 6:07 PM, Jim Dettman wrote: >> Make sure there is a times tamp field in the table, no bit fields, then relink after changes >> >> Jim >> >> Sent from my iPhone >> >> On Jan 10, 2012, at 5:49 PM, jwcolby<jwcolby at colbyconsulting.com> wrote: >> >>> I have a FE recently moved to SQL Server. Bound main form, bound child form. I entered a record in the main form, entered a record in the child form. Tried to modify the record in the main form and it gives an error "the data has changed" and refuses to allow me to change the data. I can change it directly in the tables in SQL Server. I cannot modify the record directly in the (linked) table in the FE. >>> >>> I could create the record, but not modify the record. I can modify any other record in the table, just not the one I created. >>> >>> No idea why not. >>> >>> -- >>> John W. Colby >>> Colby Consulting >>> >>> Reality is what refuses to go away >>> when you do not believe in it >>> >>> -- >>> 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