You’re offline. This is a read only version of the page.
280
I'm working in SL 2011. There is an old VBA customization, imported from SL 6.5, that has been working fine up until a week ago.
The first error message, which we got upon opening the screen, was due to the event code from the customization going AWOL. I took care of that by restoring the customization. I then ran the report successfully. I asked what happened on the system, and I was assured that no changes were made in SL, but they had installed QuickBooks on the same server.
One week later, same report, different error. The customization code is still there, but it gives me a compile error because it doesn't recognize Chr(9) (code for tab). Just to see what would happen, I replaced Chr(9) with a simple space. It was willing to print the report - for the entire database and not just the past week. I killed it before it could decimate an entire forest.
Has anyone encountered a situation in which Dynamics SL forgot how to speak VBA?
*This post is locked for comments
I have the same question (0)
Never mind. I just figured it out. I should have been using PRMSEP instead of Chr(9) - and I have a nagging suspicion that this is a lesson I had to learn before. Maybe when I restored the customization last week, I grabbed one with whiskers.
Share
Report
All responses (
Answers (
