MSFlexGrid (msflxgrd.ocx) in Access 2007 for distribution withRuntime.

[Minton M]

Ok, I'm tearing my hair out. I have written an Access-based system
that extensively uses the FlexGrid which works on my PC just fine
(because it's licensed). But it won't distribute with my Access
Runtime solution because my customers don't have a license and VBA
isn't compiled (according to Flexgrid, written by Microsoft - the same
people who wrote Access).

I don't want to use subforms because I need greater graphical control
and speed.
I just want to distribute a working OCX that will work with my Access
runtime package. Is there any way (read hack) to get this OCX to work
for my customers?

Does anyone have any idea how to do this? I'm at my wits end, having
spent hours looking through newsgroups on this. Any help would be much
appreciated!!

 

[Arvin Meyer [MVP]]

It is illegal to simply copy the FlexGrid and distribute it with your Access
app. You might consider writing a VB install app that includes the FlexGrid.

 

[Tom van Stiphout]

On Mon, 19 Nov 2007 15:16:35 -0800 (PST), Minton M

I'm not sure where you are coming from. Last time I checked
msflxgrd.ocx was allowed to be redistributed, so you can include it in
your setup program.

-Tom.

 

[Peter Hibbs]

The way I read it is that the developer gets the ActiveX license key
when he/she purchases Visual Basic or Visual Studio (or even
downloading the free Visual Basic 2005 Express version I believe) and
when he creates an application using the ActiveX control that license
key is embedded in the code for the application so that it can be used
on any other PC.

Of course, the ActiveX control still needs to be registered on the end
user's PC using regsvr32.exe (or in code). This site explains the
details.

http://msdn2.microsoft.com/en-us/library/aa751972.aspx

HTH

Peter Hibbs.

 

[Minton M]

The way I read it is that the developer gets the ActiveX license key
when he/she purchases Visual Basic or Visual Studio (or even
downloading the free Visual Basic 2005 Express version I believe) and
when he creates an application using the ActiveX control that license
key is embedded in the code for the application so that it can be used
on any other PC.

Of course, the ActiveX control still needs to be registered on the end
user's PC using regsvr32.exe (or in code). This site explains the
details.

http://msdn2.microsoft.com/en-us/library/aa751972.aspx

HTH

Peter Hibbs.




- Show quoted text -

The magic registry key (72E67120-5959-11cf-91F6-C2863C385E30) seems to
fix the problem. I'm sure it's against MS rules but the fact is that
I'm distributing compiled apps and it's their bug. Their support is of
zero help, both online and on the phone, so I'm going with this hack
until they have something better.

Given the problem has existed since 1999, I don't suspect it's the top
of their priority list anyway. For everyone else, be aware that Access
2007 doesn't distribute a FlexGrid in runtime to customers without
this key. I'm not publishing the whole thing but if you know what
you're doing, I'm sure you can figure it out.

 

[John W. Vinson]

Hi,

I am running into the same problem, i wrote an access app that heavily uses flexgrid.ocx control. Can you help on how I can install and distribute the ocx control.

Thanks
Al

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com/default.aspx?ref=ng

Alek, there are hundreds of posts here (on the public newsgroups - Egghead
Cafe is a *portal* to the much wider Usenet newsgroups) every day. Nobody can
tell what problem you're referring to. Please ask again, clarifying what
problem you're encountering.