Hello,
Under the "objects" sub-directory in "BaaN application", there are some files starting with "u". The format is-

<script name>|<some number>|<table field/table name/etc.>

These files are avialable for only customized sessions. Also, this <some number> is one for all the fields mentioned, one for all the table names, and so on. These files are created after the script is compiled, and in case the files are deleted, there is no effect on the customization.
Any idea what these files are about!!?

morpheus,

those file are like - u<module><scriptcode>

these are the where used files generated when you compile a script.

So this file contains, the where-used domains, tables, libraries etc.

I think its "OK" if you like to delete those objects but leaving them doesnt harm you too.

Yes, the deletion seems to be making no difference.
Thanks NPR!!:)

But, does that mean the where-used sessions have something to do with these files!?

But, does that mean the where-used sessions have something to do with these files!?
No. I dont think so. The where-used sessions read info from the tools tables and not from these files.

But I am still not sure why does BaaN-Tools generate these u-files and what is their purpose?

THe compiler (bic6.2) reads the program script "p..." and creates an object ("o....") if the compilation was succesfull. Besides the object, it creates a "u...." file that is read by the session "Program scripts" after the compilation. The content of this file is information about used components by the sources (program scripts and includes). After this reading (which is done directly after the compilation), the file is useless.

Regards,
Jaap Zwaan

I understand from Rao's and your post, that these files are created whenever the program scripts are compiled, and these files contain information about the components used by the sources. But, what I do not get is the reason for their creation and...

Originally posted by jaapzwaan
After this reading (which is done directly after the compilation), the file is useless.

Regards,
Jaap Zwaan

:confused:

THey are created by the compiler and read by the 4GL session "Program Scripts". This session reads those files and updates the where-used tables.

So the files are not useless, but have a limited life-cycle.

After the reading by the session, they are obsolete.

Regards,
Jaap Zwaan

If they can be created by the compilation process, why not removed as well since they are no longer used.

Jaap, if you're still working for the Baan company could it be something that you can arrange?

It would help to keep our systems clean and tidy.

Regards,
Han

Hans, I think the same holds true for the ",v" script revision files.
They can be deleted automatically when the script is deleted.

I hope Jaap will consider these minor issues.