Hello,

I've been using XL 97 for years.
I am using VBA and to set the Trusted Source", we always do:

"On the Tools menu, point to Macro and then click Security .
In the Security dialog box, click the Trusted Sources tab.
Click to select the Trust access to Visual Basic Project
check box. "

We installed XL 2007 last week so we have 2 versions of XL on each pc.

We start up the version of XL before starting our program so we can control which version of XL is used.

We are still testing ,things appear to be working as expected EXCEPT
the SECURITY menu item of the MACRO is not showing.

Is this a known conflict if you are running 2 versions of XL on the same pc?

Please, what can we do to get the SECURITY menu item back and have 2 versions of XL on the same pc?

thanks
softie

Hello,

I've been using XL 97 for years.
I am using VBA and to set the Trusted Source", we always do:

"On the Tools menu, point to Macro and then click Security .
In the Security dialog box, click the Trusted Sources tab.
Click to select the Trust access to Visual Basic Project
check box. "

We installed XL 2007 last week so we have 2 versions of XL on each
pc.

We start up the version of XL before starting our program so we can
control which version of XL is used.

We are still testing ,things appear to be working as expected EXCEPT
the SECURITY menu item of the MACRO is not showing.

Is this a known conflict if you are running 2 versions of XL on the
same pc?

Please, what can we do to get the SECURITY menu item back and have 2
versions of XL on the same pc?

thanks
softie

I have XL97 to XL2007 installed on my XP machine, and XL2003 to XL2010
on this Win7 Pro machine and my Win8.1 machine. All are working as they
should!

Try doing a 'Repair' of XL97 in ControlPanel's Add/Remove Programs
dialog. Note, though, that doing this may reset XL97 as your default
(depending on OS).

Like you, I pre-select a version before opening files. (I use a
stand-alone quick-launch toolbar similar to the old Office Shortcut Bar
name "Freebar", which is written entirely in VB6)

If you don't mind me asking.., why do you need XL97 installed?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Garry,
Thanks for the reply, I'll try it.
I, too, am a VB6 programmer.
My program needs information from the users' excel files.
Pre 2007 (ie XL 97), MS wrote the files in BIFF8 format.
Starting with XL 2007, microsoft used a new binary format called BIFF12.
Our customers have tolerated that limitation but now the time has come to support XL2007 and beyond. As I make new developments, I want to insure backwards compatibility for our xl 97 base. By having the ability to easily switch between the BIFF8 & BIFF12 file types makes supporting 2 versions realistic.

softie



On Tuesday, February 24, 2015 at 10:47:58 AM UTC-7, wrote:
Hello,

I've been using XL 97 for years.
I am using VBA and to set the Trusted Source", we always do:

"On the Tools menu, point to Macro and then click Security .
In the Security dialog box, click the Trusted Sources tab.
Click to select the Trust access to Visual Basic Project
check box. "

We installed XL 2007 last week so we have 2 versions of XL on each pc.

We start up the version of XL before starting our program so we can control which version of XL is used.

We are still testing ,things appear to be working as expected EXCEPT
the SECURITY menu item of the MACRO is not showing.

Is this a known conflict if you are running 2 versions of XL on the same pc?

Please, what can we do to get the SECURITY menu item back and have 2 versions of XL on the same pc?

thanks
softie

Garry,
Thanks for the reply, I'll try it.
I, too, am a VB6 programmer.
My program needs information from the users' excel files.
Pre 2007 (ie XL 97), MS wrote the files in BIFF8 format.
Starting with XL 2007, microsoft used a new binary format called
BIFF12.
Our customers have tolerated that limitation but now the time has
come to support XL2007 and beyond. As I make new developments, I want
to insure backwards compatibility for our xl 97 base. By having the
ability to easily switch between the BIFF8 & BIFF12 file types makes
supporting 2 versions realistic.

That's why I have so many versions installed too!

All my Excel addins are early version XLAs. They work fine in all
versions. My dictator apps use VB6 frontloaders to automate their own
XL instances, and I use a late version file to setup UI via XML if the
instance version is 11. Easy maintenance because later versions don't
mess with compatibility of addins.

You should be able to use XLAs the same way. Note, though, that
automated instances don't install addins nor enforce macro security.

My later version xlsx currently relabels the Addins tab to gsApp_Name
and my XLA runs its menus/toolbars there. All right-click context menus
work as expected, but I use context-sensitive menus anyway and so
implement an events handler class to manage MenuStates.

The later version file also customizes the Home/File tabs respectively.
This saves having to maintain 2 separate versions of my projects since
all the dictator apps use the same UI settings in XL2007/2010.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Hi Garry,
Excel 97 install options don't explicitly state that it 'repairs'

I tried the update option but the problem is still there (ie no Security tab).

Here's a link to my next step

https://www.add-ins.com/how_to_repair_office.htm

I'll let you know how that works

softie

Hi Garry,
Excel 97 install options don't explicitly state that it 'repairs'

I tried the update option but the problem is still there (ie no
Security tab).

Here's a link to my next step

https://www.add-ins.com/how_to_repair_office.htm

I'll let you know how that works

softie

Hhmmm! Good luck!

What OS is this?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

wrote in message
Hello,

I've been using XL 97 for years.
I am using VBA and to set the Trusted Source", we always do:

"On the Tools menu, point to Macro and then click Security .
In the Security dialog box, click the Trusted Sources tab.
Click to select the Trust access to Visual Basic Project
check box. "

We installed XL 2007 last week so we have 2 versions of XL on each pc.

We start up the version of XL before starting our program so we can
control which version of XL is used.

We are still testing ,things appear to be working as expected EXCEPT
the SECURITY menu item of the MACRO is not showing.

Is this a known conflict if you are running 2 versions of XL on the same
pc?

Please, what can we do to get the SECURITY menu item back and have 2
versions of XL on the same pc?

From memory although there's no problem having XL97 on the same machine with
other versions it was more complicated with VB6 because of the distinct
versions of VBA, 5 in XL97 and 6 in all later versions (OK VBA7 since 2010
but effectively the same as 6 in most respects). Also Extensibility is
different in XL97 vs all later versions, might be an issue if writing to
VBAProject or VBIDE.

If your toolbar Security button is missing back up and delete (or rename)
all *.xlb files with Excel closed. A new xlb will be created with default
menu/toolbars next time you start your XL97, maybe that will restore your
missing button.

Re BIFF8, that was current in all versions up to XL2003. Need a certain type
of mind to work with BIFF!

Re conflicts, it's important to install Excel in order oldest version first.
If you ever get a dialog something like "configuring Excel" after switching
versions, there's a registry hack to avoid that though I forget exactly
what.

Regards,
Peter T

Thanks, Peter!

From memory although there's no problem having XL97 on the same
machine with other versions it was more complicated with VB6 because
of the distinct versions of VBA, 5 in XL97 and 6 in all later
versions (OK VBA7 since 2010 but effectively the same as 6 in most
respects). Also Extensibility is different in XL97 vs all later
versions, might be an issue if writing to VBAProject or VBIDE.

I couldn't recall myself due to dropping support for XL97 back in 2002.
I now develop in 2003 only, leaving backward compatibility to
version-aware coding.

If your toolbar Security button is missing back up and delete (or
rename) all *.xlb files with Excel closed. A new xlb will be created
with default menu/toolbars next time you start your XL97, maybe that
will restore your missing button.

Re BIFF8, that was current in all versions up to XL2003. Need a
certain type of mind to work with BIFF!

Re conflicts, it's important to install Excel in order oldest version
first. If you ever get a dialog something like "configuring Excel"
after switching versions, there's a registry hack to avoid that
though I forget exactly what.

A bat file is the easiest way to toggle the default version setting in
the Registry. For example, to force 2003 as default on a system that
also has 2007...

"C:\Program Files\Microsoft Office\Office11\Office11\Excel.exe"
/unregserver
"C:\Program Files\Microsoft Office\Office12\Office12\Excel.exe"
/unregserver
"C:\Program Files\Microsoft Office\Office11\Office11\Excel.exe"
/regserver

...where "Program Files (x86)" needs to be substituted on x64 systems
running 32 bit MS Office. This 'fix' resets the registry without having
to use regedit!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

"GS" wrote in message
Thanks, Peter!

From memory although there's no problem having XL97 on the same machine
with other versions it was more complicated with VB6 because of the
distinct versions of VBA, 5 in XL97 and 6 in all later versions (OK VBA7
since 2010 but effectively the same as 6 in most respects). Also
Extensibility is different in XL97 vs all later versions, might be an
issue if writing to VBAProject or VBIDE.

I couldn't recall myself due to dropping support for XL97 back in 2002. I
now develop in 2003 only, leaving backward compatibility to version-aware
coding.

Yeah me too, though increasingly not even that.

Very occasionally I fire up XL97 and am always impressed how "snappy" it
seems to be compared with later versions, even in a very old machine.

If ever need to access any old DBF2 files it's worth hanging on to '97 or
2000

If your toolbar Security button is missing back up and delete (or rename)
all *.xlb files with Excel closed. A new xlb will be created with default
menu/toolbars next time you start your XL97, maybe that will restore your
missing button.

Re BIFF8, that was current in all versions up to XL2003. Need a certain
type of mind to work with BIFF!

Re conflicts, it's important to install Excel in order oldest version
first. If you ever get a dialog something like "configuring Excel" after
switching versions, there's a registry hack to avoid that though I forget
exactly what.

A bat file is the easiest way to toggle the default version setting in the
Registry. For example, to force 2003 as default on a system that also has
2007...

"C:\Program Files\Microsoft Office\Office11\Office11\Excel.exe"
/unregserver
"C:\Program Files\Microsoft Office\Office12\Office12\Excel.exe"
/unregserver
"C:\Program Files\Microsoft Office\Office11\Office11\Excel.exe" /regserver

..where "Program Files (x86)" needs to be substituted on x64 systems
running 32 bit MS Office. This 'fix' resets the registry without having to
use regedit!

Regserver doesn't work with 2010 on, not sure it even works for 2007 though
I'm not inclined to test!

Regards,
Peter T

I keep XL2000 installed on my dev machine because my sister still uses
it. XL97 is on an older pc and a Dell workstation. The pc is 'retired'
and I only use the older Dell for testing apps OR using SolidWorks.

Regserver doesn't work with 2010 on, not sure it even works for 2007
though I'm not inclined to test!

All I no is the batch file works for XL11/XL12 on the same machine. On
machines I have 2010 installed I want that to be the default and so I
install it *after* installing earlier versions 11/12!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

From memory although there's no problem having XL97 on the same machine with
other versions it was more complicated with VB6 because of the distinct
versions of VBA, 5 in XL97 and 6 in all later versions (OK VBA7 since 2010
but effectively the same as 6 in most respects). Also Extensibility is
different in XL97 vs all later versions, might be an issue if writing to
VBAProject or VBIDE.
Yikes!
I am writing to the VBAProject. Every instance I create a toolbar and add 3 worksheets to their workbook(s). I remove them at close.

If your toolbar Security button is missing back up and delete (or rename)
all *.xlb files with Excel closed. A new xlb will be created with default
menu/toolbars next time you start your XL97, maybe that will restore your
missing button.

There are no *.xlb files, maybe I should consider that instead of creating them for each instance. The only real change is the MRU contents of the FILE menus.

Re BIFF8, that was current in all versions up to XL2003. Need a certain type
of mind to work with BIFF!

If I had it to do over, I wouldn't use BIFF. All most all if the info can be obtained from the xl model.


Re conflicts, it's important to install Excel in order oldest version first.
If you ever get a dialog something like "configuring Excel" after switching
versions, there's a registry hack to avoid that though I forget exactly
what.

There are some creepy things things going with my program and the VB6 editor.

From memory although there's no problem having XL97 on the same
machine with other versions it was more complicated with VB6
because of the distinct versions of VBA, 5 in XL97 and 6 in all
later versions (OK VBA7 since 2010 but effectively the same as 6 in
most respects). Also Extensibility is different in XL97 vs all
later versions, might be an issue if writing to VBAProject or
VBIDE.
Yikes!
I am writing to the VBAProject. Every instance I create a toolbar and
add 3 worksheets to their workbook(s). I remove them at close.

This is the correct approach according to 'best practice'!

If your toolbar Security button is missing back up and delete (or
rename) all *.xlb files with Excel closed. A new xlb will be
created with default menu/toolbars next time you start your XL97,
maybe that will restore your missing button.

There are no *.xlb files, maybe I should consider that instead of
creating them for each instance. The only real change is the MRU
contents of the FILE menus.

These are toolbar/menu configs that are created/used by Excel. You do
not want to *mess* with these!

Re BIFF8, that was current in all versions up to XL2003. Need a
certain type of mind to work with BIFF!

If I had it to do over, I wouldn't use BIFF. All most all if the info
can be obtained from the xl model.

Not the problem so much as the version of VBA in 97 is a bigger issue.


Re conflicts, it's important to install Excel in order oldest
version first. If you ever get a dialog something like "configuring
Excel" after switching versions, there's a registry hack to avoid
that though I forget exactly what.

There are some creepy things things going with my program and the VB6
editor. Some code that communicates from my app to the xl model ,
which has worked for years, now suddenly fails. Picky, picky stuff.
Further, the vb6 editor is behaving strangely, (let's blame the new
vba). The code view window shrinks from full screen to half height.
When Scrolling thru the dropdown list of subs & functions with
direction keys, first it scrolls at the rate of a few pixels per
second then jumps to 1000 pixels per second.

MS Office 97 uses VBA5. VBA6 started in MS Office 2000. VBA7 started in
MS Office 2010. I recommend you ditch 97 and replace it with v9/v10/v11
so your VBA is compatible both ways. (VBA7 was revised for use in x64
apps. When *compiled* in x64 it won't work in x86, and vice versa!)

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

wrote in message news:
From memory although there's no problem having XL97 on the same machine
with
other versions it was more complicated with VB6 because of the distinct
versions of VBA, 5 in XL97 and 6 in all later versions (OK VBA7 since 2010
but effectively the same as 6 in most respects). Also Extensibility is
different in XL97 vs all later versions, might be an issue if writing to
VBAProject or VBIDE.

Re "Yikes! I am writing to the VBAProject. Every instance I create a toolbar
and add 3 worksheets to their workbook(s). I remove them at close."

It might not be a problem but depending on what you're doing. From memory
xl97 extensibility is v5.0 / VBEext1.olb but in all later versions 5.3 in
VBE6ext.olb. From memory everything about read/write VBProject are the same,
no problem if using late binding.

If your toolbar Security button is missing back up and delete (or rename)
all *.xlb files with Excel closed. A new xlb will be created with default
menu/toolbars next time you start your XL97, maybe that will restore your
missing button.

Re "There are no *.xlb files, maybe I should consider that instead of
creating them for each instance. The only real change is the MRU contents of
the FILE menus. "

Hmm, there should be! The xlb file is where customized toolbars are stored,
the file is always created if one doesn't exist with the default toolbars.
Not saying recreating it will solve your problem but if for some reason the
button has been removed restoring the default should. Slightly different
*.xlb name depending on xl version. You can't create an xlb yourself.

Re BIFF8, that was current in all versions up to XL2003. Need a certain
type
of mind to work with BIFF!

Re "If I had it to do over, I wouldn't use BIFF. All most all if the info
can be obtained from the xl model."

Maybe that might be easier anyway. Only reason I can think of for working
with BIFF is if Excel is N/A

Re conflicts, it's important to install Excel in order oldest version
first.
If you ever get a dialog something like "configuring Excel" after
switching
versions, there's a registry hack to avoid that though I forget exactly
what.

Re "There are some creepy things things going with my program and the VB6
editor. Some code that communicates from my app to the xl model , which has
worked for years, now suddenly fails. Picky, picky stuff. Further, the vb6
editor is behaving strangely, (let's blame the new vba). The code view
window shrinks from full screen to half height. When Scrolling thru the
dropdown list of subs & functions with direction keys, first it scrolls at
the rate of a few pixels per second then jumps to 1000 pixels per second."

No idea what's going on there but can't imagine why that would be related to
Excel

Regards,
Peter T

"GS" wrote in message ...
From memory although there's no problem having XL97 on the same
There are no *.xlb files, maybe I should consider that instead of
creating them for each instance. The only real change is the MRU contents
of the FILE menus.

These are toolbar/menu configs that are created/used by Excel. You do not
want to *mess* with these!

Just to clarify it's no problem to delete the xlb other than losing any
customized toolbars. Sometimes the xlb gets bloated or corrupt and best
deleted. A new "default" xlb will be created at next startup.

Sofie, maybe you can't find it if in a system folder, try looking in your
whatever "appdata" \microsoft (possibly microsoft shared)\excel folder

Regards,
Peter T

"GS" wrote in message
...
From memory although there's no problem having XL97 on the same
There are no *.xlb files, maybe I should consider that instead of
creating them for each instance. The only real change is the MRU
contents of the FILE menus.

These are toolbar/menu configs that are created/used by Excel. You
do not want to *mess* with these!

Just to clarify it's no problem to delete the xlb other than losing
any customized toolbars. Sometimes the xlb gets bloated or corrupt
and best deleted. A new "default" xlb will be created at next
startup.

Yes, I'm aware of this and I agree. This is different than *messing*
with an xlb file as in 'editing' it or the like...

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion