From: | Matthew and Karen Brown <browns(at)usadatanet(dot)net> |
---|---|
To: | Fred Parkinson <FredP(at)abag(dot)ca(dot)gov>, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Force commit in M$ Access? |
Date: | 2004-02-18 19:04:02 |
Message-ID: | 4033B722.6010904@usadatanet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi Fred,
You might try the following code in whatever handler you wish (button
click, etc):
DoCmd.DoMenuItem acFormBar, acRecordsMenu, acSaveRecord, ,
acMenuVer70
This will save the current record.
-- Matt Brown
Fred Parkinson wrote:
>Folks
>
>Does anyone know if it is possible, when using an Access bound form
>against a postgresql table, to force changes to commit?
>
>When the user navigates to a new record Access updates the linked
>postgres table, but due to a design flaw in the data structures, my life
>would be easier if I could force the changed data to update before the
>user navigates to a new record.
>
>My initial solution was to issue an UPDATE query whenever the user
>changed the offending data, but that results in the error
>"You and another user have updated the same data, do you want
>to:Discard changes, Copy to clipboard..." (something like that)
>as soon as the user closes the form or moves to a new record.
>
>(Yes, I know the correct answer is to fix the flaw, but the managers
>here want to slay dragons with beebee guns and don't want to spend
>money.)
>
>Thanks in advance for your help!
>
>Fred Parkinson
>Grand Canyon Software
>For
>The Association of Bay Area Governments
>510-464-7931
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>
>
Attachment | Content-Type | Size |
---|---|---|
browns.vcf | text/x-vcard | 304 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew and Karen Brown | 2004-02-18 19:23:42 | Re: column "oid" does not exist |
Previous Message | Fred Parkinson | 2004-02-18 18:41:57 | Force commit in M$ Access? |