MSFlexGrid: The subject is not trusted for the specified action 9

[ettienne]

When I add an MSFlexGrid to a VBA form I get an error message: The subject is not trusted for the specified action.

This has worked perfectly before and now a lot of customers are reporting the same error, so I suspect a Microsoft updated has something to do with it.

 

[OzFoxy]

Microsoft Critical Update KB960715 is the culprit. I'm no expert in 'killbits' but this update prevents Active X controls from working. In Control Panel / Add Remove Programs (show updates), go to the update, then click on the link to get to the Microsoft site. The explanation is there, along with some remedies.
I am using MSFlexGrid in an Access 2003 app and have had to remove the update to keep it working.
Does anyone know of a replacement for MsFlexGrid that has similar functionality?

 

[HughLerwill]

It would seem logical that the Controls within the update(s) mentioned in thread222-1525512 will not be killed; however that update may have its own issues.

 

[ettienne]

Dear Microsoft,
WTF were you thinking...

OK so it seems they have kindly blown MSFlexGrid out of the water as well as some other controls.

 

[HughLerwill]

Ref XP SP3 Prof, Excel 2003 SP3, VB6 SP6 and Update KB960715 installed.

I took the chance of installing the Dec 2008 security update for vb6 (mentioned in my previous post) onto one of my machines today.

Before installing the vb6 update, I got 'The subject is not trusted for the specified action' when trying to embed a FlexGrid onto an Excel UserForm.

After installing the vb6 update the FlexGrid appears on the UserForm normally. I have not tested the FlexGrid on the UserForm extensively but it seems to be responding to basic property changes as expected.

Don't know if this is much consolation for non VB6 users but thought the information may be useful to some.

 

[ettienne]

I installed the VB6 update and now I get "Element not found" when I add a grid to a form.

 

[HughLerwill]

Does ...

Known issue

http://support.microsoft.com/kb/957924/en-us

...help?

 

[ettienne]

Nope, I read that and checked for .exd files.

 

[OzFoxy]

What I have gleaned from other forums is that if you have VB6 installed and do the Update Rollup of Nov/Dec 2008, later versions of the OCX's are installed which are not affected by the latest 906715 update.
Users who have copied the later msflxgrd.ocx onto the machines running their Access 2003 Apps have reported problem solved.
Which is good for those with a machine with VB6 on. No good to anyone without VB6.
The solution to everyones problem would be for Microsoft to make the later OCX's available for download. Too easy?
And if they don't someone else should.

 

[HughLerwill]

Re. Excel UserForm usage it may be interesting to note that Grid32.ocx and the Sheridan Threed (albiet unsupported) Controls from vb5 do not appear to be completely outlawed (yet) by the KB960715 update.

 

[ettienne]

I got my flexgrid back after deleting all EXD files using a DOS command:
del c:\*.exd /s

Apparently the search in Explorer does not find all the files, why am I not surprised.

 

[FossilFool]

I'm not familiar with EXD files, what do they do? I'm a little hesitant to delete them all willy nilly, could this have repercussions for other programs?

Man, what a pain. This is crazy.

 

[ettienne]

They are temporary files, they are safe to delete.

 

[FossilFool]

Thanks ettienne. I had already just uninstalled KB960715 in Vista, and now the app works fine now. It wasn't so easy on my XP PC, the update was not listed with the other programs and it took a system restore point to a date earlier than this update, last week.

I'm wondering if Windows will keep trying to install this update and this problem will keep arising again...

For users, I assume it would be better to delete the EXD files rather than uninstall the update? I'm sure they will be leery of doing either. As they probably don't understand what's going on, it simply makes the application and programmer seem less professional. Sucks....

thanks again.

 

[FossilFool]

XP on my system just did an automatic update, and though I did a system restore to last week, the MSFlexGrid problem came back.

I just deleted all of the EXD files using the command 'del c:\*.exd /s' but I get the same error.

I'll have to restore to last week again, and make sure Windows does not automatically update. Am I making any erroneous assumptions here, anybody?

thanks.

 

[HughLerwill]

Fossil - Do you have VB6?

 

[FossilFool]

Yes, I have VB6, and MSFlexGrid worked in VB6 applications fine... but my problem application is with VBA in AutoCAD OEM. I can't put the grid onto a user form without the 'trusted' error, and none of the apps that previously worked fine will work now without uninstalling the update (vista) or going back to a restore point (XP). This is what I *think* is the situation. Any thoughts are appreciated!

 

[HughLerwill]

>Yes, I have VB6

Have you installed the update for vb6 covered in

http://support.microsoft.com/kb/957924/en-us

? If you have not take care to read thread222-1525512 first. Some users have reported problems with the updated WinSock and Chart controls; especially the latter.

 

[ettienne]

What about users who do not have VB6?
Is there a workaround to get the flexgrid going again?

 

[HughLerwill]

ett - I've been looking on Google for downloads of the new versions of the .ocxs since Saturday and I've only found one in a dodgy place; I did not go there. Plenty of other sites apparently offering ocx downloads but only the old versions, I guess that will change soon.
Currently, and notwithstanding licencing issues, it seems if you don't have VB6 you may need a friend who does.