Mark
asked on
The espresson On Click you entered as the event property setting produced the following error
I get the error below when a user attempts to open a file on disk using the GetOpenFileName() function:
The espresson On Click you entered as the event property setting produced the following error: License information for this component not found. You do not have an appropriate license to use this functionality in the designed environment.
* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro.
This program works fine on all but one workstation in the office. It even runs fine on the offending workstation until the user attempt to open a file. I have the following declaration in the program:
Private Declare Function GetOpenFileName Lib "comdlg32.dll" Alias "GetOpenFileNameA" (pOpenfilename As OPENFILENAME) As Long
Why would this one computer be blowing up on this? As usual, the error message sounds like it is telling me something, but I can't decipher its meaning.
The espresson On Click you entered as the event property setting produced the following error: License information for this component not found. You do not have an appropriate license to use this functionality in the designed environment.
* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro.
This program works fine on all but one workstation in the office. It even runs fine on the offending workstation until the user attempt to open a file. I have the following declaration in the program:
Private Declare Function GetOpenFileName Lib "comdlg32.dll" Alias "GetOpenFileNameA" (pOpenfilename As OPENFILENAME) As Long
Why would this one computer be blowing up on this? As usual, the error message sounds like it is telling me something, but I can't decipher its meaning.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It turned out that it was not comdlg32.dll causing the problem, but use of a 3rd party progress bar dll that I attempted to call just before the comdlg32. I eventually figured that out by commenting out the code to the progress bar and everything else worked file.
The solution was to register this dll as MessHallMan sugested, but jefftwilley's link gave me the actual "how to" command to do that: regsvr32. So, I'll split the points. Running regsvr32 with the path to my rouge dll fixed the problem.
The solution was to register this dll as MessHallMan sugested, but jefftwilley's link gave me the actual "how to" command to do that: regsvr32. So, I'll split the points. Running regsvr32 with the path to my rouge dll fixed the problem.
ASKER