CommonDialog Control invalid license error question

[kelly d via AccessMonster.com]

So I'm doing a little form design at work the other day and I go to add a
commondialog control and I get this error that says something like I dont
have a valid license for this activeX control. or something like that. I dont
ever get this problem at home so a little research discovers that aparently
the extra I kicked-down for the developers edition allows me to use the
commondialog control but at work they just got the regular ol' office sweet
so they dont have permission to add commondialog controls in access.
my question is, if I take my project home and add a commondialog control
there then take my project back to work, am I going to get an error when my
work machine goes to run the form that the commondialog control is on that I
added from home.
cuz it seems to me that would be silly cuz I imagine alot of developers have
the proper licensing to add that control while alot of clients that app's are
developed for dont have that level of Access. if that were the case then it
would be kinda pointless to even use the commondialog control cuz you never
know what level of licensing your client will have.

thanks.

 

[kelly d via AccessMonster.com]

p.s. aparently I was typing faster than I was thinking.
when I typed 'sweet' I meant 'suite'
(it's been a long day.) lol

 

[Larry Daugherty]

Hi,

There is a better way! Get rid of the common dialogs control and
implement the API based alternative. The solution is at
http://www.mvps.org/access/api/api0001.htm

you'll have to put in a bit of your own effort to get it working in
your applications. When you do, copy the module into each new
application.

By using the API you avoid all versioning issues of Access, the
control and Windows.

HTH

 

[kelly d via AccessMonster.com]

thanks for the reply Larry.
You are absolutly correct. the API call would be alot easier and I looked
into it a bit before posting.
the only tiny bug in the logic is, I need that daughnting and dastardly
printer dialog on an AC2000 machine, and for the life of me, I just cant seem
to find any code samples of how to get the printers hdc thru API's. so I was
hoping I could just cheat and add the commondialog control.

thanks

 

[kelly d via AccessMonster.com]

in case anybody wants to know,
yes it worked. I added a commondialog control at home where I have proper
license to add one, took it to work where proper licensing doesnt exist, and
the commondialog control that I added at home works just fine. so if anybody
runs into this prob about not being able to add a commondialog control cuz
you dont have a copy of access with proper licensing, if you know another
developer that can add them, just add the commondialog control on their
Access and it'll work just fine for ya.