Determining if a Reference is Needed

[jmcclain]

Over the past several weeks a co-worker and I have built a pretty good access app. We started testing it on some user machines and have consistently noticed that two references are missing on their machines.

We are not sure exactly what these references are doing anyway (or why they were clicked).

The two references are:
Microsoft ActiveX Data Objects Recordset 2.7
Microsoft Common Dialog Control 6.0 (SP3)

We've 'unclicked' them and haven't noticed any problems (so far!).

Is there a way that I can:

1) See what functionality each of these references provide - to determine whether we are using it or not

or

2) See if I've got code in my app that is going to bomb, without going testing every single scenario?

Any advice would be appreciated.

 

[MIKElaw]

The Common Dialog is the gismo that you see in any (most) Windows applications when you click to Save or Open a file. However It's not included with Access 2000, and I don't think it was with 97 either. However it appears to be with VB. I have spoken to Microsoft about it and although you may have the OCX file it won't work because you can register with the registry but you can't 'license' it because MS don't sell one so if you ever call it there will be an error. Which I suspect answers your question.

 

[Rolliee]

The developer's package wizard will show you the names of the files that MUST be present on a given P.C. WROX says we have the right to distribute such runtime files.

Rollie E