<i><font color="#663300">
Perhaps I am just missing something. As it is I will override the click behavior in ifileuserprefbar by changing it to call my old 6.0 version of isaviuserpreferenceform.
</font></i>
Greetings Scott,
Somebody on the forum asked if there were good reasons not to convert to v.61... and I think you're starting to make a case. If you are extensively hooked into the Savi classes, maybe you want to delay converting.
My own impression of the v.61 project was to put CB on a diet. To reduce the number of classes brought into a startup application. If you start re-hooking the savi classes to your projects there is no harm, but it is not a part of the original goal.
Re: preference form. I never display it. An event object updates the registry and continues with the startup. I always have edited the dbpaths table in a browse.
Have you ever seen AppStrt.app work? You put a mirror copy of application as it appears on the client out on the network. Everytime the user starts up appStrt compares the files on the client to the mirror files on the network. If they differ... the client is updated. The user doesn't need to update anything. In fact, I distribute installation CDs that contain the appstrt.exe but not the application exe. The first time the user starts up the newest exe is installed and we have no version problems. If this went too fast, I can slow down.
Re: security and menus. You should find very little to change if you use the aSecCtl library for your application form controls. Since we're still making adjustments, I would welcome any comments. Particularly if this is a priority for you.
James Sayer
©2001 James Sayer |
