mastersesci
New Member
- Joined
- Feb 10, 2011
- Messages
- 7
I did a small project for a local company that imports data from 2 source files (2 sets of 1000+ rows) and then looks for matching rows based on identifying characteristics.
The project needed a small change because one of the source file providers changed their date entries to text strings. I changed the code to use DATEVALUE and checked the macros on my computer without incident (around 1400 rows were populated).
When I sent the file back to the company, the user who runs it sees less than 100 rows populate.
I had the user run the macro, save the file, and send it back to me. While she saw only 100 rows, when I opened it the file as she had sent it I saw the expected 1400 rows.
I am using Excel 2003 and she is using Excel 2010.
I had a 3rd person test the files with Excel 2007 with no problems.
Any ideas as to what settings on her computer may be causing this problem? At this point I really don't think it has anything to do with the macro coding, although perhaps it is related to macro security level?
Thanks
Christopher
The project needed a small change because one of the source file providers changed their date entries to text strings. I changed the code to use DATEVALUE and checked the macros on my computer without incident (around 1400 rows were populated).
When I sent the file back to the company, the user who runs it sees less than 100 rows populate.
I had the user run the macro, save the file, and send it back to me. While she saw only 100 rows, when I opened it the file as she had sent it I saw the expected 1400 rows.
I am using Excel 2003 and she is using Excel 2010.
I had a 3rd person test the files with Excel 2007 with no problems.
Any ideas as to what settings on her computer may be causing this problem? At this point I really don't think it has anything to do with the macro coding, although perhaps it is related to macro security level?
Thanks
Christopher