Toolkit 6 stores web links in the stock library MDB file (unlike Toolkit 5 which stores web links in a separate database.  I don't see the benefit of this change in Toolkit 6 and am curious about why the change was made.

For example, if I create a bunch of web links and then switch to a different stock library all my web links will be unavailable unless I recreate them in the new stock library.  If I do create web links in multiple libraries I'll have to maintain them separately in each individual library.

There seems to be another issue too.  The built-in web links are also stored in the stock library, but the user can not edit or delete them.  I've been told this is so a future Toolkit maintenance release can update the built-in web links as they become stale.  It seems to me, however, that a maintenance release can only update built-in web links in the *current* stock library (MDB file).  Built-in links in other stock libraries could not be fixed (Toolkit doesn't know where or even if other stock libraries exist) by a maintenance release and the user could not fix them manually (because they can't be edited).

Isn't this a problem?

-Jim Thomas