Command line option /x

[RonAbbott]

I understand this option can run a macro, but since a macro is just some vba code, is there a way of supplying the vba code instead of a macro name ?


I get an access database from a third party and want to automate a “file import macros” and “file import modules” without first installing a macro to run the file import functions.

[June7]

What do you mean by 'macro' - a .bat or .vbs executable? Why would this macro be VBA code?

Supplying VBA code to what? Install a macro where?

[CJ_London]

I think what you are saying is you have 3rd party app which contains importing routines and you want to add those routines to another db?

If so, depends on whether the 3rd party app is .accdb or .accde and whether those macro's/functions in the module are public or not.

[Gicu]

You just use the RunCode option in the called macro to run your public function doing your imports. Alternatively you can create an AutoExec macro that evaluates to passed argument in the command line call and runs the appropriate VBA code (this from MS site - replace the OpenForm with your import function calls):

Public Sub CheckCommandLine()


    ' Check the value returned by Command function and display
    ' the appropriate form.
    If Command = "Orders" Then
        DoCmd.OpenForm "Orders"
    ElseIf Command = "Employees" Then
        DoCmd.OpenForm "Employees"
    Else
        Exit Sub
    End If


End Sub

Cheers,

[RonAbbott]

To clarify:
I regularly get a third party (password protected) access database with selected tables that I want to export to my access database (which has no password requirements).
I know the user name and password of the third party database, but would prefer not to have to log in and export the tables.
Instead the ideal would be to use a macro or VBA code to import the tables into my access database, but get "unauthorised" message when trying to import from the third party database.
So my other option is to get some code into the third party database (via a /x switch that takes VBA code instead of a macro name) so that the exporting of the selected tables (maybe 20 tables?) can be done automatically.
The only way I seem to be able to do this at present is to log in to the third party database and import a macro that has the export functions, and then to run that macro from within the third party database. Not ideal.

[Gicu]

Ron,
You can open the third party db in VBA using DAO and supplying the password, have you tried it?
https://stackoverflow.com/questions/...has-a-password
Cheers,

[RonAbbott]

Ron,
You can open the third party db in VBA using DAO and supplying the password, have you tried it?
https://stackoverflow.com/questions/...has-a-password
Cheers,

Thanks - that's helpful, though am using Access 2007 and I didnt think you could import from an open database (?)

The next answer in that link might also help me - as the data from the third party will end up in a Microsoft SQL table.
So rather than first getting the tables out of the third party database into my access database and then upload them to SQL, I'll try transferring the third party tables directly into the SQL tables via DAO

[pbaldy]

Post 7 was moderated, I'm posting to trigger email notifications.

[CJ_London]

If you have linked tables to your sql db if transferdatabase doesn’t work you can just use a query

[RonAbbott]

OK, I used the following code but still not working - is there a way to specify the user name as well as the password ?
'Const
dbImport = Forms!Main!CPath & "\RhmDat.mdb"
'Const
sPassword = "abc123"


Dim DB As DAO.Database
Set DB = DBEngine.OpenDatabase(Name:=dbImport, Options:=False, ReadOnly:=False, Connect:=";PWD=" & sPassword)
DoCmd.TransferDatabase acImport, "Microsoft Access", dbImport, acTable, dbTable, dbTable, False
DB.Close
Set DB = Nothing

[RonAbbott]

[RonAbbott]

"You do not have the necessary permissions to use the '......mdb' object. Have your system adminstrator establish the appropriate permissions for you"
Also I am using Access 2003

[Gicu]

It seems like the file is protected with the old mdw (workgroup) security, do you know if that is the case or is it just a database password?

Cheers,

[RonAbbott]

Yes, it has an mdw and user and group security settings - there seems to be no database password

[Gicu]

Can you remove the (now deprecated) ULS from the original file? The DAO example you are trying to use was intended for the databases protected with a database password, not ULS.

https://support.microsoft.com/en-us/...rs=en-us&ad=us

Cheers,