J
jacob farino
Thanks Charles!
This works for all states EXCEPT states that begin with "i"...any
suggestions?
This works for all states EXCEPT states that begin with "i"...any
suggestions?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
David McRitchie
Rather than using AutoCorrect, I would suggest that you restrict the correction
to the column actually involved using an Event Macro to change
the entries in a specific column as entered. See the event macro under
http://www.mvps.org/dmcritchie/excel/proper.htm#upper
to the column actually involved using an Event Macro to change
the entries in a specific column as entered. See the event macro under
http://www.mvps.org/dmcritchie/excel/proper.htm#upper
J
jacob farino
Thanks David, I've found a few things very useful on your page!
Here's my current problem.
I followed the UPPER_CASE macro you listed on the below link, and it worked
perfectly when I typed it and hit run. However, excel began saving non-stop.
I had to end task to stop the program. Upon reopen, the macros have been
disabled and I cannot enable them even if I set security to low (i don't
have any signatures on the macro). So how do you suggest this be fixed? (I
have excel2002)
Here's my current problem.
I followed the UPPER_CASE macro you listed on the below link, and it worked
perfectly when I typed it and hit run. However, excel began saving non-stop.
I had to end task to stop the program. Upon reopen, the macros have been
disabled and I cannot enable them even if I set security to low (i don't
have any signatures on the macro). So how do you suggest this be fixed? (I
have excel2002)
David McRitchie said:Rather than using AutoCorrect, I would suggest that you restrict the correction
to the column actually involved using an Event Macro to change
the entries in a specific column as entered. See the event macro under
http://www.mvps.org/dmcritchie/excel/proper.htm#upper
---
HTH,
David McRitchie, Microsoft MVP - Excel [site changed Nov. 2001]
My Excel Pages: http://www.mvps.org/dmcritchie/excel/excel.htm
Search Page: http://www.mvps.org/dmcritchie/excel/search.htm
Thanks Charles!
This works for all states EXCEPT states that begin with "i"...any
suggestions?
D
David McRitchie
Hi Jacob,
There is nothing in the macro to cause a file save.
You must have something else going on, but I don't know what.
The macro you chose is a regular macro and works off of a
selection of cells, as opposed to the event macro below it.
I see from the previous reply that you must have installed all
of the state codes into AutoCorrect, and I don't see how that
could causes saving either.
All I can suggest is to complete exit Excel and try it again.
If you get into Excel and run the macro, rather than just stopping
try DeBug and see what statement it is hung up in -- hopefully,
for me, it won't be my macro.
Right click on the worksheet to see if there is code there.
Rigth click on the icon to left of the menu bar which bring up
"ThisWorkbook" and see if tehre is cde there. Use the [x] in the
upper right corner below the [X] that closes the Visual Basic Editor
to get out of the module.
If you have macros you should set the security to "Medium",
and reply each time you open the workbook. This is for your protection
against opening an Excel file without even realizing you opening an
Excel file, or in opening an Excel file that is not supposed to have
macros -- it gives you a chance to look at the macros. Setting the
security to "High" which is the default prevents macro use altogether.
When you change the setting, you have to exit the wrkbook and open it again.
--
There is nothing in the macro to cause a file save.
You must have something else going on, but I don't know what.
The macro you chose is a regular macro and works off of a
selection of cells, as opposed to the event macro below it.
I see from the previous reply that you must have installed all
of the state codes into AutoCorrect, and I don't see how that
could causes saving either.
All I can suggest is to complete exit Excel and try it again.
If you get into Excel and run the macro, rather than just stopping
try DeBug and see what statement it is hung up in -- hopefully,
for me, it won't be my macro.
Right click on the worksheet to see if there is code there.
Rigth click on the icon to left of the menu bar which bring up
"ThisWorkbook" and see if tehre is cde there. Use the [x] in the
upper right corner below the [X] that closes the Visual Basic Editor
to get out of the module.
If you have macros you should set the security to "Medium",
and reply each time you open the workbook. This is for your protection
against opening an Excel file without even realizing you opening an
Excel file, or in opening an Excel file that is not supposed to have
macros -- it gives you a chance to look at the macros. Setting the
security to "High" which is the default prevents macro use altogether.
When you change the setting, you have to exit the wrkbook and open it again.
--
A
AlfD
Hi!
Maybe you should use a dropdown box (powered by Data Validation) to ge
people to select the right abbreviation for the State. You could eve
accompany it with a list of the full names of States to avoid an
confusion/ambiguity/doubt.
Al
Maybe you should use a dropdown box (powered by Data Validation) to ge
people to select the right abbreviation for the State. You could eve
accompany it with a list of the full names of States to avoid an
confusion/ambiguity/doubt.
Al