Frontend MySQL - ( , msaccess -) EXPORTING MsAccess MySQL ( , , , ):
MsAccess, ,
, IP-, SSH ( - ). , FAQ NetSol: http://www.networksolutions.com/support/how-to-back-up-the-mysql-database-using-ssh/
BATCH EXPORT/DUMP MySQL MsAccess, FORM , , VBA sub OnClick():
Dim sTblNm As String
Dim sTypExprt As String
Dim sCnxnStr As String, vStTime As Variant
Dim db As Database, tbldef As DAO.TableDef
On Error GoTo ExportTbls_Error
sTypExprt = "ODBC Database"
sCnxnStr = "ODBC;DSN=DSNname;UID=userOnServer;PWD=pwdOnServer"
vStTime = Timer
Application.Echo False, "Visual Basic code is executing."
Set db = CurrentDb()
For Each tbldef In db.TableDefs
Debug.Print tbldef.Name
sTblNm = tbldef.Name
DoCmd.TransferDatabase acExport, sTypExprt, sCnxnStr, acTable, sTblNm, sTblNm
Next tbldef
MsgBox "Done!"
On Error GoTo 0
SmoothExit_ExportTbls:
Set db = Nothing
Application.Echo True
Exit Sub
ExportTbls_Error:
MsgBox "Error " & Err.Number & " (" & Err.Description & ") in procedure ExportTblsODST"
Resume SmoothExit_ExportTbls
, 2507. "ODBC Database" "ODBC" ( ).
: MsAccess:
1.
2.
3.
The MsAccess interface does not really care about which database engine it uses, so itβs safe practice to have 2 separate MDBs: queries, forms, macros, etc. And raw data. This way you can easily switch from a local database to a remote server. and your main application file does not contain the actual data.
source
share