| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
2003 vs 2007
I have an organization with 300 employees spread across 10 counties. We use
a time sheet designed in excel. When the time sheets are emailed in, VBA code transfers needed data from the time sheets into an "employee payroll database". Anyway, the original VBA was written in Excel 2003 and ran like greased lighting. The computers have been upgraded and everyone is now using Excel 2007. However, we still save the Excel Time Sheet files as Excel 2003 files. Anyway, the code now runs very slowly. What can I do? -- Thanks Shawn |
|
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
2003 vs 2007
1. Rewrite the VBA in EXCEL 2007.
2. Save the files as EXCEL 2007 files. Doing the above will keep everything, "clean" and consistent. If my comments have helped please hit Yes. Thanks. "Shawn" wrote: I have an organization with 300 employees spread across 10 counties. We use a time sheet designed in excel. When the time sheets are emailed in, VBA code transfers needed data from the time sheets into an "employee payroll database". Anyway, the original VBA was written in Excel 2003 and ran like greased lighting. The computers have been upgraded and everyone is now using Excel 2007. However, we still save the Excel Time Sheet files as Excel 2003 files. Anyway, the code now runs very slowly. What can I do? -- Thanks Shawn |
|
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
2003 vs 2007
Well, I converted the "end" file to a 2007 file and did a "find and replace"
changing all the .xls extensions to .xlsm extensions and that did the trick. It is back to working like greased lighting and it is dealing better with all versions of excel: 2003 and 2007. See, not all our machines have the new Office software so the program has to be back compatible. Anyway, the fix noted above worked great. -- Thanks Shawn "trip_to_tokyo" wrote: 1. Rewrite the VBA in EXCEL 2007. 2. Save the files as EXCEL 2007 files. Doing the above will keep everything, "clean" and consistent. If my comments have helped please hit Yes. Thanks. "Shawn" wrote: I have an organization with 300 employees spread across 10 counties. We use a time sheet designed in excel. When the time sheets are emailed in, VBA code transfers needed data from the time sheets into an "employee payroll database". Anyway, the original VBA was written in Excel 2003 and ran like greased lighting. The computers have been upgraded and everyone is now using Excel 2007. However, we still save the Excel Time Sheet files as Excel 2003 files. Anyway, the code now runs very slowly. What can I do? -- Thanks Shawn |
| Reply |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| Excel opens two windows (2007 & 2003 format): I want only 2003. | Excel Discussion (Misc queries) | |||
| 2003 vba to hide two grouped charts, works in 2007 but not in 2003 | Excel Programming | |||
| 2003-2007 xlsm-2003 loses worksheet commandbutton functionality | Excel Programming | |||
| 2003--2007 recognize if i'm in 2007 or 2003 via code. | Excel Programming | |||
| Excel 2007, I write macros in 2003 is 2007 similar for VBA? Pros andcons please | Excel Programming | |||
Linear Mode
