Mark A Matte
markamatte at hotmail.com
Fri Nov 19 07:49:20 CST 2004
Andy, This might sound like dancing around this issue...but could you have user click on the record to be updated...open a second query/form for just that record...save the record...and the give a message, "Your update has been saved and will be reflected next time you refresh the screen". Just a thought... Thanks, Mark A. Matte >From: "Gustav Brock" <Gustav at cactus.dk> >Reply-To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >To: <accessd at databaseadvisors.com> >Subject: Re: [AccessD] Updatable UNION? >Date: Thu, 18 Nov 2004 11:58:03 +0100 > >Hi Andy > >No, unions are read-only. If you can't go the update-behind-requery >route, I guess you are left with the temp table. > >/gustav > > >>> andy at minstersystems.co.uk 18-11-2004 10:09:56 >>> > >Morning all >I've a continuous screen which needs to list two types of order in >date >sequence. These are held on separate tables. No problem, a UNION query >does >the job fine. However the user has to tick an order to say it's >despatched, >and then the screen needs to show that information, but the recordset >is not >updatable. Presumably this applies to all UNION queries does it? Does >anyone >have a way round this or do I have to go to extracting to a temp table >and >all that jazz? > >By the way it's not practical to upodate the underlying tables and >requery >to display the depatch info because there's a lot of data on screen >and >requerying takes too long. > >-- >Andy Lacey >http://www.minstersystems.co.uk > >-- >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com