Re: forms libraries...

Isaias,

Some answers:

> I'm using forms 4.5 in Developer 2000. We currently have 2 libraries
>that are attached to most of our forms (on the file side). I'm trying to
>see if I can add a function to one of the libraries. The problem is this:
>I'm trying to make a copy of the library file and work on it locally on my
>hard drive without affecting the production version. From what I have seen
>the libraries are attached with the path removed. From reading the
>documentation, it seems that for the libraries, when the path is removed,
>the form looks at the forms45_path or Oracle_Path registry variables.

Yes, that's right. At run-time, the fmx will look for the attached library in each directory specified in forms45_path. It will first look for a plx in each directory in turn, then repeat for a pll if no plx is found.

>Is there a way to ensure that the form always grabs the version of the
library
>that is in the shortcut's working directory path (shortcuts are set up in
>Windows 95 to either run the production version of the forms or test or
even
>local copies)?

No, not unless you put the working directory in your forms45_path list, before other directory entries. This is the approach I use for testing.

> Also, I don't want to have to re-attach the libraries on
>every form that it's attached to when I make the change. Is there a way to
>do that? Thanx. --Isaias

You don't need to re-compile unless you've changed the public declaration of an existing procedure/function (changed the number or type of passed parameters). Forms 4.5 libraries are run-time libraries, ie. they're not compiled into the fmx. The fmb requires the pll at compile time only for the library's public declaration.

Hope this helps,
Neville Sweet. Received on Fri Oct 22 1999 - 07:44:46 CEST