Search results

No, I assume it's getting hung up on the TRUNCATE part. I really don't think I need to change connection strings etc. The code works fine except for the srcDB.Open line. And as far as that goes it works except for putting in the password. This code up until a month or so ago worked just fine...

And here's what happened.

I know how to comment things. I'm not completely ignorant. So you are saying I should have this as well? set srcRS = CurrentProject.Connection

I don't follow. This code takes the linked Oracle tables which I cannot access and runs update and append queries to update and append the Oracle tables with Access tables that I do have access to. Changes are made daily to the Access tables and then those changes are applied to the Oracle...

Code now looks like this: Public Sub OMS_Update() Set srcDB = CurrentProject.Connection 'srcDB.Open "database", "username", "passord" srcDB.CursorLocation = adUseServer DoCmd.SetWarnings False Set srcRS = New ADODB.Recordset srcRS.Open "TRUNCATE TABLE OI_LOC", srcDB, adOpenDynamic...

Yes, all the appropriate tables are linked to the Access database already.

Why did it work a month ago and stop working now if this is just spinning my wheels? You are going to have to elaborate on why I have to change the code.

Again, not my code. I'm not going to go changing someone elses code.

It isn't my code, I can't touch anything on the Oracle server, but it is my job to make sure this code runs everyday. I can't go changing connection strings etc. Do you have any insight as to why this one isn't working? I had gotten this problem resolved several months ago and the problem has...

Here's the code: Dim srcDB As ADODB.Connection Dim srcRS As ADODB.Recordset Dim txtStatus As String Public Sub OMS_Update() Set srcDB = New ADODB.Connection srcDB.Open "database", "username", "password" srcDB.CursorLocation = adUseServer After this it just goes into calling a bunch of...

Here is where your problem is Col; you seem to think that everybody in America is that way. What you don't realize is that it is our politicians and media that behave in that manner. Most of us here in the USA would like them to leave us alone as well, but you see these power hungry socialists...

About the economic stimulus: Sometime this year, we taxpayers may again receive an Economic Stimulus payment. This is an exciting program. I'll explain it using the Q and A format: Q. What is an Economic Stimulus payment? A. It is money that the federal government will send to...

I found the solution, but haven't been able to perfect it. I am calling the macros from a batch file and setting up the task scheduler to run the batch file. If I run the batch file manually while I am sitting there it runs fine. It ran fine from the task scheduler for a couple of days, but...

I have written a batch file that calls shortcuts to 4 macros in 4 different Access databases. The goal is for this batch file to run every night and update the 4 databases. The problem that I am running into is that for one of the databases it will run the macro completely through and then throw...

Ya, that made things worse.

I'm not, I have just referenced the secondary db and called the function. If I run the function in the secondary database by itself it runs fine; if I call it from the primary database it seems to get things out of order and hangs up. I'm going to try opening the secondary database with...

Yes, I can open the secondary db from the primary, its the doing stuff that I'm having trouble with. I figured out this most recent problem. I had the module named the same as the function. I'm not much of a programmer, that is poor practice I guess.

Option Compare Database Public Function Runmacros() DoCmd.RunMacro "Daily AS400 TNS Update Macro" End Function This is the secondary database code, it just calls the macro Function Update() Call Runmacros End Function This is the primary database code that calls the other function.

I tried writing a module in one of the secondary databases and referencing the database in the primary database and calling the module from there. It then gave me an error on the call function that said it was expecting a variable or procedure, not a module. What does this mean and how do I make...

Yes, I tried to SetWarnings False. It's not an Access warning, it is an office warning, it goes deeper than the code that I am running.