It would be difficult to do a search across the whole database for what you are looking for regardless. If you search for unit on hand you'll find it in 20 places and you'll still have to guess which one you really want. Also, unless we come up with a standard method of description you will be hard pressed to guess what someone has used as the description of a field. I would think that it would be much more valuable to have the information associated with the fields themselves in the database so that one could figure out what a field is when they need it most. That is, when they are building a report or screen. Even then, I could see the use for at least a list of the tables with descriptions in an external file so that looking up the right table to use is easier. On that note, it might be nice to get a list of which reports reference which tables. I would think that that would be the most important information to have external to the database.
Still, I don't mean to suggest that I'm opposed to having the info externally. It would certainly be good to have the info in both internal and external form. I wonder how easy it is to programatically insert the field descriptions into BTrieve. That way people could work on the descriptions in the excel file and then import them into the database. That way we've got it both ways.
Quote from David Waldmann on 02/07/07 at 04:48:01:
If it were going to be only in one place I'd rather have it in an external file so I can search the entire database at once, rather than first trying to guess which table it's in and then looking through all the fields. However, it would be nice to have the description in the database (as some already are).
Pages: 1 2
Modify Forms (Read 2154 times)
