What you want is two different screens - one for you and one for your co-workers. Kinda like a login screen where each person would enter a code and based on that code certain processes and screens would be customized just for them. For example, if you put in your login number, you would see all the fields. If a co-worker keyed in their login number, they would see only fields that had data.
That makes sense...
I was thinking that you just wanted to hide blank fields. That made no sense, since no one would be able to add data to those fields thru the admin panel.
The place to start would be when admin.cgi is called, the user has to enter a login number. In the admin_html.pl file the build_html_record_form routine ( which is in the db_utils.pl file ) gets called by the add, modify, validate, etc routines. That seems like the logical place to test for blank fields based upon the login number.
Maybe some of the perl experts in the forum could help you.
Gene
That makes sense...
I was thinking that you just wanted to hide blank fields. That made no sense, since no one would be able to add data to those fields thru the admin panel.
The place to start would be when admin.cgi is called, the user has to enter a login number. In the admin_html.pl file the build_html_record_form routine ( which is in the db_utils.pl file ) gets called by the add, modify, validate, etc routines. That seems like the logical place to test for blank fields based upon the login number.
Maybe some of the perl experts in the forum could help you.
Gene