I've been putting together an automated spreadsheet that has external data sources to SQL. I have been having some strange problems with it between versions of Excel. Unfortunately, the company's standard is 2003 but quite a lot of the company use 2007. I have been developing this report on 2007, the server that runs the automated version of the spreadsheet runs 2003 (and cannot be upgraded beyond 2003 as it is running Server 2000!).
The template opens fine on my 2007 machine and all development work has been run on my machine including the downloading of data. The VBA script runs something like
I have one simple (but large table). It has dates across the top (formatted in hh format). I would like the associated table to format according to the day and also to format differently when there is a public holiday. So I have built a table with the holidays and named the relevant cells as "Holiday_Valid".
I have the following formula in the conditional formatting;
Where D11 has the current day in question and Holiday_Valid is a list of public holidays. Since there is a cell for each hour of each day I am using "int()".
There is a second conditional format to format Sundays differently as below;
My problem is that these both work well....but then after a few minutes the whole sheet crashes with those dreaded "Trying to recover your data" and "Excel will restart" etc.
I have removed references to named ranges and so far - so good....but this means putting the validation table in the same sheet as the main table. In the past I have been able to use named ranges (albeit not in such convoluted formulae), but now it seems that it is not working any longer.
When I open the recovered sheet, all the conditional formatting has been removed and the message from the repairs is that there was some invalid conditional formatting.
Extensive web searches did show some issues with conditional formatting using names ranges....especially with frozen panes....which I need use with a sheet this big.
I've created a workbook with code to email it to a reviewer then back to the originator when reviewed (along with other editing functions etc.). The problem - The originator is working in Excel 2003, the reviewer in 2007. The macros work great until the reviewer sends it back. I have not been able to figure out which FileFormat:= ???? to use when I SaveAs prior to emailing as an attachment. My Excel 2003 doesn't recognize the .xlsm file and other formats are eliminated the vba/macro coding
I have some schedules set up with multiple formulas and macros (originally setup in 2003) however when attempting to make this a 2007 file when I go to copy a sheet to create another schedule I get the message A formula or sheet you want to move or copy contains the name xx, which already exists on the destination worksheet. Do you want to use this version of the name? To use the name as defined in the destination sheet, click yes. To rename the range referred to in the formula or worksheet, click no, and enter a new name in the Name Conflict dialog box.
I would like to send a .xls file created in Excel 2007 to a user who will work with this file on a PC that runs Excel 2003. Will they be able to open and use a file created in a newer version of Excel?
My company used to have Excel 2003. I had a PivotTable in a worksheet that accessed data in another, completely different worksheet. When we converted to Excel 2007, I saved many of my Excel files from .xls to .xlsm. My PivotTable that once accessed data from another .xls file is still trying to access that same .xls file. What I want, though, is for it to access the new .xlsm file.
I have a spreadsheet that collates a list of data from week order and puts them in a graph. I have a macro created that basically does the graph, it works fine in 2003 but not in office 2007. I get an error "Run Time Error '1004' Application-defined or object-defined error, then when I click the debug button it highlights "ActiveSheet.ChartObjects.Delete". I'm not sure if when its trying to create a new graph its attempting to delete the old one and isnt deleting it? The full code for the macro is below:
Sub updateStuff() Dim searchResult As Range 'Result of the find operation - to check if it has worked or not Application.ScreenUpdating = False If SheetExists("OTIF Chart") Then Application.DisplayAlerts = False Sheets("OTIF Chart").Delete Application.DisplayAlerts = True End If Sheets("OTIF's").Select Range("B4:N4").Select Selection.Copy Sheets("Graph").Select Range("B1").Select................................
I created a Macro in 2007 and it turns out I needed to develop it in 2003. Now none of my code works and I am trying to convert it. I would appreciate any assistance determining what needs to be corrected and how to correct it. Here iare two samples that is repeated throughout my code.
'Delete anything currently in spreadsheet Application.CutCopyMode = False Range("A2:N1048576").ClearContents Range("A2").Select ActiveWorkbook.Save
For a particular requirement I want to utilise the colours. ANd therefore I need to know, how many colours are present in the Colour Palette in both 2003 and 2007 and which colours would be same if I make the File in 2007?
I'm struggling constantly with the Excel 2007 I use, and the Excel 2003 that another group uses.
I'm dealing with large files; 200000 to 300000 rows often.
I wish there was a setting or way to automatically force excel 2007 to create a file in 2003 format.....meaning I want 260000 rows to automatically be divided up into 4 sheets limited to 65K each. 260001 rows would be put into 5 sheets, so that I could save it as an excel 2003 file.
Is there also a way to do this from access 2007 exported to excel?(I know that's an access question and probably outside the bounds of this board).
I am trying to find a method of adding a combo box and populate it that works for Excel 2000, 2003 and 2007. The following works for Excel 2007 but did not work on a machine installed with Excel 2003.
With Sheets("Tasks").ComboBox1 .AddItem "By Task Number" .AddItem "By Date Task Assigned" .AddItem "By Date Due for Completion" .AddItem "By Status" .AddItem "By Status and Date Due for Completion" End With
Is is possible to write code that is compatible on both versions.. ie
If Application.Version > 11 Then ' excel 2007 code Else ' excel 2003 code End If I have developed a reporting spread for a client which contains automated chart generation, all done with VBA. I have read numerous threads of issues when upgrading.
What they want is the chart VBA to be upgraded so that it can be run on both versions.
I have run into a brick wall with InStr, Replace, and Len. I take the data from the active cell (formatted as text). I need to cleanup the data and do further massaging of it. In testing cleanup code, I get behavoirs and results I simply don't understand and can't figure out from hours searching forums many places.
The following simplified example commented code can be cut/pasted into a new spreadsheet module and should be self-explanatory. Example data is in the comments. Data is entered by multiple users and multiple sources. Therefore there is no control over the input quality so extraneous characters and multiple repeated periods and spaces can show up anywhere.
With the kind help of this forum, I put together a nice business tool that has a fair amount of automation via macro buttons, etc. It works great in XL 2007 but some users are having issues in 2003. I appreciate this is quite general but are there significant conflicts / differences with coding in these two different versions?
in adapting the previous code to MS Excel 2007. I have found that the "application.filesearch" object no longer exist in 2007! The code goes to a file path and extracts the text and places the data in the specified excel column.
i installed office 2007 beta version on my computer (for testing) together with the already existing office 2003. now the default program of my excel files is excel 2007 beta version (not excel 2003). can i change this behavior so that when i open an excel file the default program would be excel 2003 instead of excel 2007 and whenever i want to open a file using excel 2007 i do so by right clicking the file & choosing excel 2007 from the open with list.
I need to find out which version of excel i am using in macro.I mean whether it is 2003 or 2007.Because i need to put 2 diff codes according to the version of excel.Can any one please provide me the macro code to findout the version of Excel.
I have a fairly simple macro that takes a few seconds on my XP-computer with Excel 2003 but takes several minutes on my Vista-computer with Excel 2007.
The XP-PC has 2GB memory, the Vista-PC only 1GB, but it's hard to believe it's only that. Is Excel 2007 so much slower than 2003?
The macro makes quite extensive use of the .rows(Rownr).Delete method. Is the fact that 2007 has 1 million rows against the 65536 of 2003 the culprit? It has to shift much more data up when deleting a row, no?
I recently upgraded from Excel 2003 to 2007, and the worksheet change procedure that i have embedded in my worksheet no longer fires when the criteria are met. If and if I fix it to work in 2007, will it still work in 2003?
Here is my procedure:
Private Sub Worksheet_Change(ByVal Target As Range) Dim rngCell As Excel.Range If Not Intersect(Target, Range("C19:R19")) Is Nothing Then For Each rngCell In Intersect(Target, Range("C19:R19")) If rngCell.Value = "BLACK" Then MsgBox "Please select a shading style", , "Shading Style Required" End If Next rngCell End If End Sub
i downloaded the beta version of the office 2007 for testing. can i install this version alongside my existing office 2003 version. i want to have the 2 versions installed on my computer so that i can choose between the versions when opening a file.