Registered: 1158198299 Posts: 5,507
Reply with quote
I would like the facility to store off-line libraries in the procedure file itself. Having an absolute path for the library makes it impossible to distribute a Procedure file and associated Libraries without specific instructions as to how to publish. For example, customers have often published the Procedure File before the Library file, so the Library is not picked up. having to explain the difference in the files is something I wish I did not have to do. Library files are not ‘published’ to the database like a procedure file, it is merely stored as a blob. It is only accessed when publishing a procedure file, whereupon it is retrieved and all associated segments etc are updated. If you publish the procedure file and then the library file, the procedure is using the old version of the library, not the one you just published. __________________ Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.