|
-
May 25th, 2004, 08:34 PM
#1
Thread Starter
Lively Member
xl97, xl2002
I have an excel 97 file that was mistakenly opened and saved in xl2002. No changes were done to the file, it just ran the save command.
Now when I open it in 97, on each save I get a box saying it was saved in another version of excel and asking if I want to lose my changes, etcs.. How do I tell Excel that this is an Excel 97 file again and not an Excel 02 file?
-----
#VBA, VB 6 Professional Edition, Office XP Developper. Excel 97, Excel 2000, Excel XP
I miss my VIC 20.
Never should have upgraded to my commodore 64. ...
-
May 25th, 2004, 11:28 PM
#2
Hey Fiddler, can't you do a save as and select 97 format file type
instead of a regular save?
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
May 26th, 2004, 07:29 PM
#3
Thread Starter
Lively Member
You'd think that would work, wouldn't you?
Tried two approaches - both failed
From within Excel 02, opened my file and then Save As, file type Excel 97.
First got an error that said I was unable to save to this file format with a locked VBA module. So I unlocked my VBA module, and tried to save again as Excel 97 format, got a "Document Not Saved" information error screen pop up.
Then I tried from within Excel 97, and forced the Format to Excel 97 file type. Up comes my warning saying that this file is from a later version and that data will be lost if I continue. I continue anyway. So in theory, this should be in 97 format, but if I try to save again or to reopen the file, I get the ever so annoying message that this file is from a later version and that data will be lost if I continue.
So my question remains - are their any properties or flags within the file that determine the file type? Anyone have any other approaches to this?
-----
#VBA, VB 6 Professional Edition, Office XP Developper. Excel 97, Excel 2000, Excel XP
I miss my VIC 20.
Never should have upgraded to my commodore 64. ...
-
May 27th, 2004, 12:17 AM
#4
Would it be possible to create a new Excel 97 workbook and
copy/recreate the 2002 version. This would be an original 97
version workbook with the same contents as the mistake 2002
version workbook. Then open with 2002 and make some changes
and save as 97 version format.
Not too sure on what flags there may be to designate the version
differences.
In hindsight, maybe you could add a safty check to make sure
they are not allowed to save as 2002?
HTH
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
May 27th, 2004, 04:08 PM
#5
Thread Starter
Lively Member
If I knew what the 2002 flags were, I would cut/paste from 02 workbook into an XL97 workbook.
If I paste code or formatting that is 02 only, then I will only get the same result.
Actually, I decided my course of action - restore from backup and redo the changes that I've done over the past week. That way I am confident that I did not miss something that would adversely effect the performance of my program.
And as to the stop save as 2002 idea, easy to code for 02, but the same code will generate an error under 97 as the file type did not exist then.
btw: cool news to share. just discovered that my software company was recipient of a Innovation leader of the year award for our area because of our latest software release. Fun stuff.
-----
#VBA, VB 6 Professional Edition, Office XP Developper. Excel 97, Excel 2000, Excel XP
I miss my VIC 20.
Never should have upgraded to my commodore 64. ...
-
May 27th, 2004, 04:25 PM
#6
Congradulations!
What about checking if being saved as 97 then let the save
happen? Else it doesn't matter what version, just deny it.
PS. do we get any honerable mention in your programs credits? JK.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|