[AccessD] Open File Dialog Box Call Fails

You might try sending him your version and have him back his dll (or full
system) up, unregister his version, copy yours to where his was, and
register it.  This is a big YMMV.

If his is different, you might could try the reverse on your system.  If it
worked, then recompile your app and then have him re-install.

If the different versions is what is causing the problem, then you have just
entered that infamous place lovingly called "DLL Hell."

I am just shooting in the dark here, but this is some of the stuff that I
would investigate.

Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin -
Beach Access Software
Sent: Wednesday, June 22, 2005 10:45 AM
To: Access Developers discussion and problem solving
Cc: Ben Saltzer
Subject: Re: [AccessD] Open File Dialog Box Call Fails


I suppose he could check the properties on his comdlg32.dll.  If it doesn't 
match the one I'm using (where the app still works) where could he find the 
old one?

TIA

Rocky

----- Original Message ----- 
From: "Bobby Heid" <bheid at appdevgrp.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, June 22, 2005 7:39 AM
Subject: RE: [AccessD] Open File Dialog Box Call Fails


>I wonder if it is some sort of service pack that has hosed something?  
>Or  maybe he installed something that put a different version of 
>comdlg32.dll?
>
> Bobby
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky 
> Smolin - Beach Access Software
> Sent: Wednesday, June 22, 2005 10:26 AM
> To: AccessD at databaseadvisors.com; dba-tech
> Cc: Ben Saltzer
> Subject: [AccessD] Open File Dialog Box Call Fails
>
>
> Dear List:
>
> I have a client who's selling an app I wrote where I use the code from 
> the ADH to call the file open dialog box:
>
> Declare Function adh_apiGetOpenFileName Lib "comdlg32.dll" _  Alias 
> "GetOpenFileNameA" (ofn As tagOPENFILENAME) As Boolean
>
> I haven't worked on the app for several months and it's been very 
> stable until a couple of weeks ago when this call began to fail with 
> no error message.  Just didn't open the dialog box.  Then it failed on 
> another computer.  Then on another one.  Now no computer in his place 
> runs this api.
>
> I went over to his place and stepped through the code and sure enough 
> it goes to the api call and then goes right through the api call 
> without opening the dialog box.
>
> If we try to drop the common dialog control onto a form in design view
> from
> the additional tools list in the toolbox we get a message that says the 
> OLE
> server isn't registered.
>
> So I need to figure out
>
> 1) how to get the OLE server registered (unregistered first I suppose) 
> and see if that is somehow hosing the file open dialog box
> 2) figure out if there's a problem with comdlg32.dll
> 3) see if I can determine why this app suddenly went south so that it 
> doesn't happen at one of his customer sites.
>
> He's using Access 2000 SP-3 but also fails in AXP.  The app fails on 
> both W2K and WXP.  He's pretty careful about virus scanning.  I don't 
> think it is a virus even though it behaves like one.  Is it possible 
> that it got hosed by an automatic windows update?
>
> Any clue as to what's going on here would be greatly appreciated.
>
> MTIA,
>
> Rocky Smolin
> Beach Access Software
> http://www.e-z-mrp.com
> 858-259-4334