Replies

Hey Pat. Thanks for joining the conversation.

Yes, you are right. Clicking the Save password checkbox will overcome having to type in your password each time–ON MOST ODBC CONNECTORS. This is an AS/400 connector–and it is a little flakey. The Save password checkbox doesn’t, and creating a file-based connection (*.dsn) is highly unstable. You have to use a machine-based connection, which really sucks if your app needs to be available on multiple desktops.

I appreciate everyone’s responses. Hopefully, someone will come up with a snippet of coding that will do the trick. I tried creating a ConnectionString, complete with UID and PWD, but didn’t know how to tie it to an already linked table, OR delete the link with the table and create a ConnectionString that will connect to an existing AS/400 file.

I haven’t figured it out yet. I’m sure it can be done, I’m just not sure how. I think that there is a way to save userid and password information into a DSN file.

I haven’t figured it out yet. I’m sure it can be done, I’m just not sure how. I think that there is a way to save userid and password information into a DSN file.

Hey Catherine. Glad you could join the discussion.

Actually, the /user and /pwd switches apply only to the mdb itself. I am going against an external ODBC datasource (an AS/400).

Hey Catherine. Glad you could join the discussion.

Actually, the /user and /pwd switches apply only to the mdb itself. I am going against an external ODBC datasource (an AS/400).

Ok, I figured out that my problem was in accessing an external database referenced in my code. The reason it just hung was because it was waiting for a password. This was never a issue during development since my computer is automatically authenicated to this database. I moved the project over to a server to run it as a scheduled job overnight. The server does not automatically authenticate to this external data source (its an AS/400).

So now I need to figure out a way to code in this connection. I will submit another thread if I can’t figure it out. Thanks to everyone who submitted answers to this.

Ok, I figured out that my problem was in accessing an external database referenced in my code. The reason it just hung was because it was waiting for a password. This was never a issue during development since my computer is automatically authenicated to this database. I moved the project over to a server to run it as a scheduled job overnight. The server does not automatically authenticate to this external data source (its an AS/400).

So now I need to figure out a way to code in this connection. I will submit another thread if I can’t figure it out. Thanks to everyone who submitted answers to this.

Hi Charolotte!

Below I’ve included a screen of the macro–very simple. There are no parameters required for the function. And the function only calls a procedure in the module. It is this procedure that actually does any work.

I do have quite a lengthy declarations section for this module. Would this be the “preconditions” you refered to?

Hi Charolotte!

Below I’ve included a screen of the macro–very simple. There are no parameters required for the function. And the function only calls a procedure in the module. It is this procedure that actually does any work.

I do have quite a lengthy declarations section for this module. Would this be the “preconditions” you refered to?

Thanks for the response, Wendell.

According to the help file, a command line switch of /x macro starts and runs the specific macro. Have I misunderstood this?

My command line: “C:Program FilesMicrosoft OfficeOffice10MSACCESS.EXE” ddfile01dataddrMarketingMORPT_data.mdb /x mUpdateData

mUpdateData is actually a macro, whose only statement is to call a function.

My next step will be to add statements to my code to write to a log file in order to see where everything hangs up, and if it even gets to the function at all.

Thanks for the response, Wendell.

According to the help file, a command line switch of /x macro starts and runs the specific macro. Have I misunderstood this?

My command line: “C:Program FilesMicrosoft OfficeOffice10MSACCESS.EXE” ddfile01dataddrMarketingMORPT_data.mdb /x mUpdateData

mUpdateData is actually a macro, whose only statement is to call a function.

My next step will be to add statements to my code to write to a log file in order to see where everything hangs up, and if it even gets to the function at all.

Great sugguestion, Hans. Works like a charm.

Great sugguestion, Hans. Works like a charm.

I love this board and the quick responses. Thanks, Hans!

I love this board and the quick responses. Thanks, Hans!