Re: Force commit in M$ Access? - Mailing list pgsql-odbc

From Philippe Lang
Subject Re: Force commit in M$ Access?
Date
Msg-id 6C0CF58A187DA5479245E0830AF84F420AFBFF@poweredge.attiksystem.ch
Whole thread Raw
In response to Force commit in M$ Access?  ("Fred Parkinson" <FredP@abag.ca.gov>)
List pgsql-odbc
Hello,

You can use this routine:

---------------------------
Sub cmdSaveFct()
On Error GoTo cmdSaveFctError

    DoCmd.DoMenuItem acFormBar, acRecordsMenu, acSaveRecord, , acMenuVer70

cmdSaveFctExit:
    Exit Sub

cmdSaveFctError:
    MsgBox Err.description
    Resume cmdSaveFctExit
End Sub
---------------------------

Philippe Lang


-----Message d'origine-----
De : pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] De la part de Aaron Spike
Envoyé : mercredi, 18. février 2004 20:39
À : Fred Parkinson; pgsql-odbc@postgresql.org
Objet : Re: [ODBC] Force commit in M$ Access?

On 18 Feb 2004 at 10:41, Fred Parkinson wrote:
> Does anyone know if it is possible, when using an Access bound form
> against a postgresql table, to force changes to commit?

This is probably a bad idea but
SendKeys "+{ENTER}"
might just work.

Pressing Shift+Enter in a form is supposed to commit changes to the current record. I'm not sure if there is a cleaner
VBAhook into that functionality. 

Aaron Spike


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match



pgsql-odbc by date:

Previous
From: "Aaron Spike"
Date:
Subject: Re: Force commit in M$ Access?
Next
From: Matthew and Karen Brown
Date:
Subject: Re: column "oid" does not exist