Deployment on Users PCs - MS Access 2003 |
Post Reply |
Author | |
bardaroart
Newbie Joined: 11 February 2007 Status: Offline Points: 17 |
Post Options
Thanks(0)
Posted: 12 February 2007 at 5:40pm |
I just bought the calendar control - it works well on my development pc - what will I need to do to make it work on other users' PCs?
Will copying the .ocx file be enough, or is there a regserver command needed? Users will be running a MS Access 2003 application..., with newer ones using MS Access 2007 Thanks - Anthony |
|
sserge
Moderator Group Joined: 01 December 2004 Status: Offline Points: 1297 |
Post Options
Thanks(0)
|
You'll have to copy and register OCX into users' PCs.
And also you'll have to provide the OCX with licensing information. The best way is to embed it into your application. See the following article for help: http://www.codejock.com/support/articles/com/general/g_3.asp -- WBR, Serge |
|
rgracie
Groupie Joined: 12 November 2006 Status: Offline Points: 75 |
Post Options
Thanks(0)
|
Serge, I'm using the control in an MS Access 2002 (XP) .mde... Should I be suppling the licensing information? I have had no complaints about any licensing issues yet... Robert |
|
sserge
Moderator Group Joined: 01 December 2004 Status: Offline Points: 1297 |
Post Options
Thanks(0)
|
Regularily you have to provide a lic file togethjer with Calendar.OCX
or set license as a string in CalendarGlobalSettings. But Access may cache license information on development stage. To be sure I recommend you set license using CalendarGlobalSettings See for details: https://forum.codejock.com/forum_posts.asp?TID=6072 -- WBR, Serge |
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |