ExcelBanter - How to distribute Control files (OCX) to users?

1 - You will almost certainly need to create a small distribution package.
Even if it just consists of a batch file which copies and registers the
relevant controls (REGSVR32). My memory is a bit vague on the datagrid
control that comes with VB. It was originally developed by a company called
Apex (they are still around and make great tools like this) for Microsoft
and bundled with VB. The reason I'm mentioning all this is because some of
the controls give licence not found errors when you try to use them in
Excel. The grid may be one of them.

Either way before going any further I'd check all this with a little pilot
deployment to a fresh PC which doesn't have the controls you require
already.

2 - The code will be virtually identical to how you would have done it in
VB. The control's properties and methods remain constant irrespective of
the container application.

I'd check that the datagrid components of VB (assuming this is what you're
using) will actually work correctly outwith the VB environment. The quick
answer is they should (as they are ActiveX's) but I did some work with this
years ago and have a nagging feeling there are some hidden issues.

Failing all this and budget/infrastructure allowing it look at the new
standalone version of the control I mentioned.

--
Regards,

Bill Lunney
www.billlunney.com

"Terence" wrote in message
...
Hi,

In Visual Basic, if we include the controls such as
DataGrid in the project, the corresponding file (OCX file)
must be distributed to the enduser's computer in order to
make it work in other computers beside the developer's
computer. We create a setup package and run it on
enduser's computer for distribution.

(1) I would like to include a DataGrid in my Excel macro
program. Do I have to do the control file distribution for
the endusers also? If I have to do it, how?

(2) Can anyone tell me how to put data of an ADO recordset
into a DataGrid in Excel macro?

Thanks in advance.

Terence