Steve
I’d go with Access is that is working for you. By the way, variables lose their values if the project encounters an unhandled error. Try using error traps in every procedure just in case.
FYI, Access VBA variables won’t lose their values if the application is an ACCDE or MDE, but error handling is still a must.
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT http://thatlldoit.com
MS Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852
My Nothing-to-do-with Access blog
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Friday, December 04, 2015 7:02 AM
To: MS Access Pros List
Subject: [MS_AccessPros] Part Question, part rant, part OT
I have recently inherited a PowerPoint file with 100+ shapes that have embedded Excel files that are linked to MS-SQL server views (yeah, I know ...)
There is a VBA procedure that is supposed to loop and and refresh these things. But the procedure keeps having unexplained issues: it can't find the server (it's there), commands to excel about backgroundquery=false run but don't change the property, variables don't hold values (I have a counter figuring I could start over at the last bad one, not at the beginning) ... Basically, it seems to me the Powerpoint VBA engine is a pile of dung; I can call any other program in the Suite from Access and not have anywhere near this amount of problems ...
Which leads to the question, should I just run the code from Access, calling PPT and Excel from our old friend (this all ver 2010 btw.)
thanks for letting me vent,
Steve Conklin
Posted by: "Bill Mosca" <wrmosca@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (17) |
Tidak ada komentar:
Posting Komentar