Unintended change to Excel VBA code

  • Thread starter Thread starter Conrad Carlberg
  • Start date Start date
C

Conrad Carlberg

A few days back, I posted a similar message to the main Access newsgroup,
due to a situation with a networked Access database, concerning VBA code
behind an Access user form. The feedback suggested that I re-save the Access
..mdb file as an .mde, and that seems to have solved the issue.

Now it's happened again, but in an Excel workbook. The workbook has much VBA
code, and the subroutines run in response to custom menu items. These subs
have been running for several years with no problems. The sole user of the
workbook has now encountered a compile error and tells me that the VBA shows
her a single exclamation point highlighted in that (dratted) yellow. (The
Access error involved an unintended period.)

Anyone here seen a character like a period or exclamation point inserted
unintentionally and systemically into an Excel VBA module? I really doubt
that it was done maliciously and intentionally, although of course that's
possible.
 
Thank you, Chip. I haven't seen or heard of it either. I really hate to
believe that a user is doing this but I guess I have no alternative to
protecting the project.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Excel Macro to un-mute Audio/speakers. 15
Excel VBA - Problem with Closing Print Preview 0
VBA, Sometimes Loads, Sometime Disabled - Why? 2
How to Keep Excel Sheet Formatting On a CSV Sheet with vba 1
VBA Error Handling 4
Check if Excel is open in Word VBA 0
Copy a worksheet to a new workbook 6
vba code does not run 3

Back
Top