 | |
ms-access97 & sql server2005 - error "the data has been changed"
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: ms-access97 & sql server2005 - error "the data has been changed" -
02-25-2008
, 10:52 PM
|
ms-access97 & sql server2005 two tables tblItem tblItemFeature form frmItem contains subform frmItemFeature each form is based on their respective table creating new record and filling in two bound fields works fine creating new record, filling in first field, filling in field in subform and filling in second field, produces error the data has been changed another user edited this record and saved the changes before you attempted to save your changes reedit the record both tables have a timestamp fields, per other discussions in this news group |
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
#12
| |||
| |||
|
|
lyle fairfield <lylefa1r (AT) yah00 (DOT) ca> wrote: Either table have triggers on them? That wasn't Roger that was Roy. Which picture was that in, Lyle? Revenge of the Palomino! guffaw Tony |
only <neigh> or <whinny>.
I guess we'll see if there's anyone here who's familar enough with the
radio cowboys of the early 40's to know why.
Here's a hint. I listened to a show with Tony in it from 17:45 to 18:00
(5:45 pm to 6:00 pm) from WSLB, Ogdensburg every afternoon in 1945 and on
April 12 it was interrupted by a famous announcement. My friend, Donald and
I went out onto the street to tell people this news but no one believed
seven year olds. We should have said, "But it's true, man (or soon will
be)!"
And some people say there's nothing new to be learned on CDMA!
Lyle
(Always the Lone Ranger)
#13
| |||
| |||
|
|
I'm back in my childhood cowboy days and Tony never said <guffaw> then, only <neigh> or <whinny>. I guess we'll see if there's anyone here who's familar enough with the radio cowboys of the early 40's to know why. Here's a hint. I listened to a show with Tony in it from 17:45 to 18:00 (5:45 pm to 6:00 pm) from WSLB, Ogdensburg every afternoon in 1945 and on April 12 it was interrupted by a famous announcement. My friend, Donald and I went out onto the street to tell people this news but no one believed seven year olds. We should have said, "But it's true, man (or soon will be)!" And some people say there's nothing new to be learned on CDMA! |
his master were both gone on to the Great Beyond by then. And, going on to
the Great Beyond might be a good lead-in to the other event you mentioned.
#14
| |||
| |||
|
|
Roger wrote: On Feb 25, 4:56 pm, "Rick Brandt" <rickbran... (AT) hotmail (DOT) com> wrote: Roger wrote: On Feb 25, 3:45 pm, Roger <lesperan... (AT) natpro (DOT) com> wrote: if I go to the subform control on the main form and I add 'me.refresh' to its exit event, I don't get the error why ? Either table have triggers on them? -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com nope I just used the access wizard to export the design / data from the mdb to sql server nothing else What datatype (on the server) are the fields in the primary keys? *If these don't have exact Access equivelants then it can sometimes round them and get confused. *I doubt that would have if you exported them from with the wizard, but it's still worth checking. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt * at * Hunter * dot * com- Hide quoted text - - Show quoted text - in sql2005 |
[itemId] [int] IDENTITY(1,1) NOT NULL,...
CREATE TABLE [dbo].[tblItemFeature](
[itemId] [int] NOT NULL,
[itemClassId] [nvarchar](2) NOT NULL,
[featureId] [int] NOT NULL,....
in msaccess
tblItem.itemId is autonumber
tblItemFeature.itemId is long integer
.itemClassId is text
.featureId is long integer
#15
| |||
| |||
|
|
Roger <lesperan... (AT) natpro (DOT) com> wrote: ms-access97 & sql server2005 two tables * *tblItem * *tblItemFeature form frmItem contains subform frmItemFeature each form is based on their respective table creating new record and filling in two bound fields works fine creating new record, filling in first field, filling in field in subform and filling in second field, produces error * *the data has been changed * *another user edited this record and saved the changes before you attempted to save your changes * *reedit the record both tables have a timestamp fields, per other discussions in this news group Just guessing. *Is the primary key of those tables also on the form? Tony -- Tony Toews, Microsoft Access MVP * *Please respond only in the newsgroups so that others can read the entire thread of messages. * *Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm * *Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hidequoted text - - Show quoted text - |
the forms
#16
| |||
| |||
|
|
in sql2005 CREATE TABLE [dbo].[tblItem]( [itemId] [int] IDENTITY(1,1) NOT NULL,... CREATE TABLE [dbo].[tblItemFeature]( [itemId] [int] NOT NULL, [itemClassId] [nvarchar](2) NOT NULL, [featureId] [int] NOT NULL,.... in msaccess tblItem.itemId is autonumber tblItemFeature.itemId is long integer .itemClassId is text .featureId is long integer |
changes directly in table link datasheets I have definitely seen what you
are describing. If I change a row, move to a different row, and then change
the first row again I will get that message just about every time.
I don't recall seeing it occur on a form, but perhaps I just never performed
the sequence you are describing.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.