[AccessD] AccessD Digest, Vol 115, Issue 5

It is already there in the System32 folder.
You just have to change the location of it in tools | references

I have used it on a number of Win 7 x64 systems without issues.


At 03:14 PM 9/13/2012, you wrote:
>Date: Thu, 13 Sep 2012 14:33:27 -0400
>From: jwcolby <jwcolby at colbyconsulting.com>
>To: Access Developers discussion and problem solving
>         <accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Windows 7
>Message-ID: <505226F7.4080904 at colbyconsulting.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>AFAIK it shouldn't matter where it resides when it is 
>registered.  Registering provides the
>indirection to allow your app to just call the DLL.  The registry 
>then "figures out" where the DLL
>is actually located.
>
>John W. Colby
>Colby Consulting
>
>Reality is what refuses to go away
>when you do not believe in it
>
>On 9/13/2012 1:57 PM, Tony Septav wrote:
> > Hey All
> >
> > Just bought a new machine, came with Windows 7.  A client asked 
> me to update
> > an application we have been constantly updating for the last 10 
> years.  What
> > was MicroSoft thinking. A lot of my code and MicroSoft ActiveX controls
> > don't work anymore. I used the Common Dialog, ImageList and TreeView
> > controls (God help me what else). I had to download the ComCtl32.ocx and
> > ComDlg32.ocx because they do not come with Windows 7. Now I am having no
> > luck registering these items in the Windows/System32 folder. A couple of
> > (online)  recommendations suggested they should be placed in the
> > \Windows\SysWow64 folder and then registered, My question is, on 
> the clients
> > older machines they will not have a SysWow64 folder. Any suggestions how I
> > can register these files from the System32 folder???
> >
> >
> >
> > Thanks
> >
> > Tony Septav
> >
> > Nanaimo,BC
> >
> >
> >

Robert L. Stewart
www.WeBeDb.com
www.DBGUIDesign.com
www.RLStewartPhotography.com