Michael Brösdorf
michael.broesdorf at web.de
Tue Jul 6 09:39:26 CDT 2004
Francis, THAAAANK YOU!!! Unfortunately I already started to go unbound, but guess what: it's pain in the.. and I am more than willing to stay 'bound'. That solution is so simple! However, do you have any information regarding performance implications (a new (temp) table is created every time the trigger fires)? Michael -----Ursprüngliche Nachricht----- Von: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]Im Auftrag von Francis Harvey Gesendet: Dienstag, 6. Juli 2004 16:18 An: 'dba-sqlserver at databaseadvisors.com' Betreff: RE: [dba-SQLServer] #Deleted-Problem (Cross-posted) Michael, I hope you didn't spend all weekend on this as there must be a better answer then going unbound. I am guessing the KB was 275090? It would help if we could read exactly what Microsoft wrote about the problem. Working from that, I did a Google search and ended up with this (WFW), http://groups.google.com/groups?q=275090+access&hl=en&lr=&ie=UTF-8&selm=elcr f%23VVEHA.384%40TK2MSFTNGP10.phx.gbl&rnum=1 which suggests a method for recoding triggers to ensure @@IDENTITY. Since I am just getting back to speed after the holiday, I don't trust myself to think through whether this solves your problem. Does this seem like a workable approach? Francis R Harvey III WB 303, (301)294-3952 harveyf1 at westat.com > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf > Of Michael Brösdorf > Sent: Friday, July 02, 2004 8:50 AM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] #Deleted-Problem (Cross-posted) > > > Dear group, > > > I have a problem with my Access2000-App. The Backend is SQL > Server 2000 > > A bound form is linked to Table A. Table A has an > insert-trigger, that creates a record in table B. > Both tables have an ID-Field (A_ID and B_ID). > > Whenever I save a new record in the bound form, it either > immediately displays #Deleted# in every field, > or displays an old record(!). > However, the new record is created correctly. > > There's a knowledgebase article, describing that problem. It > states, that Access tries to re-select the > new record using the ID value. It looks like that it is using > the ID-value of table B instead that of table A to do the > re-select. If it finds a record with that ID it displays that > in the new row on the bound form. If it does not find it, the > form displays #Deleted#. > > Is there any way to tell the trigger on table A not to return > the ID of the new record in table B? <snip> _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com