|
-
Aug 2nd, 2000, 10:53 AM
#1
Thread Starter
New Member
Hey, people
I have a calendar object in a form that works fine on any machine in the IT department, but the problem I am facing right now is that this application needs to operate on the production floor on a terminal with a user with less rights on the system.
The problem that exists is that when the form activates (from another forms button_click event-handler) the calendar object fires a run-time error:
Run-time Error '429': You do not have an appropriate
license to use this functionality .. blah blah blah ..
So to remedy this I used :
Debug.Print Licenses.Add ("MSACAL.Calendar")
And that didn't necessarily work, but it was enough to fire off another error :
Run-Time error '739': Cannot add control 'MSACAL.
Calendar'. Dynamically adding ActiveX Controls
requires the use of the ProgId which can be
different from LibraryName.Class for some controls.
The ProgId for this control is 'MSCAL.Calendar.7'.
Ok, so that didn't work, but I did get the ProgID which I aptly put in a Licenses.Add statement such as:
Licenses.Add "MSCAL.Calendar.7"
So now I am using a UserControl Run-Time License but that in turn gave me the error:
Run-Time error '733': The control 'MSCAL.Calendar.7'
cannot be added to the Licenses collection, because
it is already referenced by the project. It is not
necessary to add controls that are referenced by the
project.
So I can conclude that my Calendar object is being licensed at run-time. This object works without fail on my machine, as I said before, but it won't work on the production machine where it needs to be running. The network administrator tried using the administrator logon to that particular machine and we got the same error as the floor worker so now I believe it's either a problem localized with that machine or it could be a software issue.
My question for those of you that have read this far and not fallen ill to the ennui of this malady is what have you done to have fixed this and what in particular can I do or look for that could possibly affect this problem? I need your help and I need it fast !!
"The God of VB has Spoken"
Senior Developer Analyst
Siemens Energy & Automation
Alpharetta, GA
-
Aug 2nd, 2000, 11:55 AM
#2
Lively Member
Have you tried the vbusc.exe fix available from msft
which fixes licensing issues?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|