| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Differente .xls files generated when VBE window closed vs open
While debugging some generated spreadsheets that are picked up by a third
party system, we found that the actual byte code of xls workbooks generated in vba in Excel differ depending on wether or not the VBE window is open or closed. Has anyone run across this? The files generated when the VBE window is open are always about 8k larger than when the VBE window is closed. Looking at the files with a hex editor, the files are completely different. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This causes us to open the VBE window programatically before saving the file in code. When opening both files separately in Excel all modules, properties etc are identical. File is being saved with Application.VBE.MainWindow.Visible = True ( or False) xlNewBook.SaveAs FileName:=strOutputPath & "_" & strWorkBookName, _ FileFormat:=-4143, Password:="", WriteResPassword:="", _ ReadOnlyRecommended:=False, CreateBackup:=False, TextCodePage:=1100 Thanks in advance, Mark |
|
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
Differente .xls files generated when VBE window closed vs open
Hi Mark,
Indeed an xls that has been 'exposed' to an open VBE is saved with additional data, even if no code or modules ever added. Such a file will include "_VBA_PROJECT_CUR", I posted a routine that'll check all files in a folder for that. http://tinyurl.com/2jn79e As I mentioned in the thread, that string merely confirms the file has been 'exposed' to the VBE, it may or may not include code or inserted modules. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This seems curious, why not, does that third party app want to add a project password perhaps. Regards, Peter T "Mark" wrote in message ... While debugging some generated spreadsheets that are picked up by a third party system, we found that the actual byte code of xls workbooks generated in vba in Excel differ depending on wether or not the VBE window is open or closed. Has anyone run across this? The files generated when the VBE window is open are always about 8k larger than when the VBE window is closed. Looking at the files with a hex editor, the files are completely different. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This causes us to open the VBE window programatically before saving the file in code. When opening both files separately in Excel all modules, properties etc are identical. File is being saved with Application.VBE.MainWindow.Visible = True ( or False) xlNewBook.SaveAs FileName:=strOutputPath & "_" & strWorkBookName, _ FileFormat:=-4143, Password:="", WriteResPassword:="", _ ReadOnlyRecommended:=False, CreateBackup:=False, TextCodePage:=1100 Thanks in advance, Mark |
|
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
Differente .xls files generated when VBE window closed vs open
Thanks Peter, I will take a look - the external system does some strange
things with workbooks... "Peter T" wrote: Hi Mark, Indeed an xls that has been 'exposed' to an open VBE is saved with additional data, even if no code or modules ever added. Such a file will include "_VBA_PROJECT_CUR", I posted a routine that'll check all files in a folder for that. http://tinyurl.com/2jn79e As I mentioned in the thread, that string merely confirms the file has been 'exposed' to the VBE, it may or may not include code or inserted modules. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This seems curious, why not, does that third party app want to add a project password perhaps. Regards, Peter T "Mark" wrote in message ... While debugging some generated spreadsheets that are picked up by a third party system, we found that the actual byte code of xls workbooks generated in vba in Excel differ depending on wether or not the VBE window is open or closed. Has anyone run across this? The files generated when the VBE window is open are always about 8k larger than when the VBE window is closed. Looking at the files with a hex editor, the files are completely different. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This causes us to open the VBE window programatically before saving the file in code. When opening both files separately in Excel all modules, properties etc are identical. File is being saved with Application.VBE.MainWindow.Visible = True ( or False) xlNewBook.SaveAs FileName:=strOutputPath & "_" & strWorkBookName, _ FileFormat:=-4143, Password:="", WriteResPassword:="", _ ReadOnlyRecommended:=False, CreateBackup:=False, TextCodePage:=1100 Thanks in advance, Mark |
|
#4
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
Differente .xls files generated when VBE window closed vs open
Solved this in case anyone is interested. In code added a dummy module to
VBComponent...seems to force save in Biff8 format. "Mark" wrote: Thanks Peter, I will take a look - the external system does some strange things with workbooks... "Peter T" wrote: Hi Mark, Indeed an xls that has been 'exposed' to an open VBE is saved with additional data, even if no code or modules ever added. Such a file will include "_VBA_PROJECT_CUR", I posted a routine that'll check all files in a folder for that. http://tinyurl.com/2jn79e As I mentioned in the thread, that string merely confirms the file has been 'exposed' to the VBE, it may or may not include code or inserted modules. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This seems curious, why not, does that third party app want to add a project password perhaps. Regards, Peter T "Mark" wrote in message ... While debugging some generated spreadsheets that are picked up by a third party system, we found that the actual byte code of xls workbooks generated in vba in Excel differ depending on wether or not the VBE window is open or closed. Has anyone run across this? The files generated when the VBE window is open are always about 8k larger than when the VBE window is closed. Looking at the files with a hex editor, the files are completely different. The problem is that for some reason the 3rd party system will not handle the file correctly unless it gets the format that is generated when the VBE window is open. This causes us to open the VBE window programatically before saving the file in code. When opening both files separately in Excel all modules, properties etc are identical. File is being saved with Application.VBE.MainWindow.Visible = True ( or False) xlNewBook.SaveAs FileName:=strOutputPath & "_" & strWorkBookName, _ FileFormat:=-4143, Password:="", WriteResPassword:="", _ ReadOnlyRecommended:=False, CreateBackup:=False, TextCodePage:=1100 Thanks in advance, Mark |
| Reply |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| 2 excel files open in same window | Excel Discussion (Misc queries) | |||
| how do i set Excel 2003 files to open in own window | Excel Discussion (Misc queries) | |||
| How can I open from Web Excel Files in a separate Window? | Excel Discussion (Misc queries) | |||
| Multiple files open in same window | Excel Discussion (Misc queries) | |||
| How do I open excel files in a new window | Excel Discussion (Misc queries) | |||
Linear Mode
