Thank you Andrew...why do i want to refresh a link table, because i've read several discussions about "interupted/Dropped ODBC connection in the midle of a process...(i think it means to long process)" or something like that,,,and they said that is a weakness of ODBC connection. So i think "refreshing a linked table" (before execution) would much help for this, not all the linking tables in the FE, just the table that we want to process...what do you think about it?
Regards
Hendra Agestha
--------------------------------------------
Pada Ming, 9/3/14, yahoo@craven.de <yahoo@craven.de> menulis:
Judul: [MS_AccessPros] RE: Refresh a Linked table
Kepada: MS_Access_Professionals@yahoogroups.com
Tanggal: Minggu, 9 Maret, 2014, 11:00 PM
Hi Hendra,
The same restriction applies to the QueryDefs collection,
you can only change the SQL or Connect if you assign/create
a QueryDef object and then manipulate the parameters,
otherwise they are readonly.
In my experience, you don't normally need to do a
RefreshLink after changing the Connect string (at least with
Linked SQL Server Tables), it might however be "best
practice" to do so.
Yours,
Andrew
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (7) |
Tidak ada komentar:
Posting Komentar