|
SQL Losing Data
We're using SQL Server 7 with an Access 2000 MDB as a front end with ODBC
linked tables. I recently created a new set of tables for the app, and users
are complaining that unsaved data is being lost when they move to a new
record. This seems to be the case when there are multiple users. When there
is a single user using it, we don't seem to have that problem.
It seems that we had this problem when we first converted from an MDB back
end to a SQL 7 back end, years ago, but we haven't had this problem in a
while. These are the first "entirely new" tables created in several years,
and we seem to be having that problem again.
Is this something with SQL 7 when it's dealing with new tables? Any ideas on
what to do?
Thanks!
Neil
Wed, 12 Jan 2005 19:53:02 GMT
"Neil Ginsberg"
|
Re: SQL Losing Data
I'm using a bound Access form, the same as I am with the other forms that
have been working for years. There
Thu, 13 Jan 2005 02:10:57 GMT
"Neil Ginsberg"
|
Re: SQL Losing Data
You know, that might be it. I did forget to put the timestamp column in (the
other tables were convert
Thu, 13 Jan 2005 02:12:20 GMT
"Neil Ginsberg"
|
Re: SQL Losing Data
Neil Ginsberg wrote:
> We're using SQL Server 7 with an Access 2000 MDB as a front end with ODBC
> linked tables. I recently created a new set of tables for the app, and users
> are complaining that unsaved data is being lost when they move to a new
> record. This seems to be the case when ther
Thu, 13 Jan 2005 08:43:24 +0000
Trevor Best
|
Re: SQL Losing Data
Neil Ginsberg wrote:
> Well, that took care of the issue with the "record has been changed" error
> message. And, though the other error was intermittent so I can't directly
> test it, I'm sure having the timestamp field will take care of that other
> one, as well. Thanks again for your help!
D'OH! that'll teach me to read the whole thread before replying :-)
--
This sig left intentionally blank
Thu, 13 Jan 2005 08:44:23 +0000
Trevor Best
|
Re: SQL Losing Data
Access and SQL is a sick combination.
I have had such strange problems with A2K and SQL2K.
The worst thing is some of these problems are intermittant.
Sometimes these problems go away with a Jet engine update or an MDAC update.
And then sometimes new ones of a similar vein pop up with updates.
"Neil Ginsberg" wrote in message
news:RmFFd.6743$Ii4.5233@newsread3.n
Fri, 14 Jan 2005 08:49:14 -0800
"User"
|
Re: SQL Losing Data
Actually not really. I still think you are missing the
point. You often have to do the same thing with other data
sources that support timestamps when using ODBC linked
tables and Access. You have to kluge the data source so that
Access doesn't get confused. You can find more
Fri, 14 Jan 2005 10:38:55 -0700
Sue Hoegemeier
|
Re: SQL Losing Data
Okay then. I actually do have a pretty good understanding of
how Access works and in particular how it works when linking
tables via ODBC to various data sources and the issues that
can be encountered. I did know what you meant about the
record saving when moving around on the form. And I'm aware
of the order of events and what fires when in what order and
under what conditions. So I'm not so sure that it's
necessarily related to my not really understanding how
Access works.
I guess what you have seen fail and what I have seen fail in
Access is different but I'd rather move on for now.
-Sue
Fri, 14 Jan 2005 12:00:02 -0700
Sue Hoegemeier
|
Re: SQL Losing Data
OK. Well, thanks again for your input!
Neil
"Sue Hoegemeier" wrote in message
news:4s4gu057js7l2aa0hns6p34hai82o7a13v@4ax.com...
> Okay then. I actually do have a pretty good understanding of
> how Access works and in particular how it works when linking
> tables via ODBC to various data sources and the issues that
> can be encountered. I did know what you meant about the
> record saving when moving around on the form. And I'm aware
> of the order of events and what fires when in what order and
> under what conditions. So I'm not so sure that it's
> necessarily related to my not really understanding how
> Access works.
> I guess what you have seen fail and what I have seen fail in
> Access is different but I'd rather move on for now.
>
> -Sue
Fri, 14 Jan 2005 19:09:16 GMT
"Neil Ginsberg"
|