I am able to run an access “program” which prints a report using a stored procedure, this works fine. (the "program" is just a .bat file which calls an access database that has an AutoExec macro which sets warnings off, opens a form. On the open form event, it prints a report, closes the form (no save), set warnings on, and closes the access application (as exit, no saves again).
I am able to link sql tables into that report and pull specific data into the report and print that just fine.
When I add another linked table (could be the 2nd, 4th, 10th, or first, doesn’t’ matter), which is linked to access and not to sql, the “program” craps out. What happens is msaccess.exe is loaded in the task manager, an .ldb file is created, but nothing happens. As soon as it gets to the part where it would print the report, it fails. I know this also because I have done a kill(“c:\test.doc”) before the printing and that part would work (just as a test to see where it was failing). However, running the .bat file (which only calls the database to run) works fine…only when you try to run the database as a stored procedure is when it fails.
So, one solution is to import everything into sql, which should be done anyways, but could cause multiple problems down the road. Have you ever heard / ran into this problem? Could this be some sort of weird permissions issue?
Do you think setting up a trigger would resolve this issue? (run executable program upon insert into sql table).
I am not sure where to post this as it is specifically a problem with access linked table, but only doesn't work from a sql stored procedure.
I am running access 2003 and am thinking about upgrading to 2007 to see if that works. The linked tables will be coming from an access 97 database.
I am able to link sql tables into that report and pull specific data into the report and print that just fine.
When I add another linked table (could be the 2nd, 4th, 10th, or first, doesn’t’ matter), which is linked to access and not to sql, the “program” craps out. What happens is msaccess.exe is loaded in the task manager, an .ldb file is created, but nothing happens. As soon as it gets to the part where it would print the report, it fails. I know this also because I have done a kill(“c:\test.doc”) before the printing and that part would work (just as a test to see where it was failing). However, running the .bat file (which only calls the database to run) works fine…only when you try to run the database as a stored procedure is when it fails.
So, one solution is to import everything into sql, which should be done anyways, but could cause multiple problems down the road. Have you ever heard / ran into this problem? Could this be some sort of weird permissions issue?
Do you think setting up a trigger would resolve this issue? (run executable program upon insert into sql table).
I am not sure where to post this as it is specifically a problem with access linked table, but only doesn't work from a sql stored procedure.
I am running access 2003 and am thinking about upgrading to 2007 to see if that works. The linked tables will be coming from an access 97 database.
