I can't quite tell from your description, but I think you have some structural problems in how you are organizing your database. How about describing what you are trying to keep track of.

Fields are independent of the layouts on which they appear, you don't need "new" fields for each layout. If you wish to keep track of information for a number of different computers, you would typically have a separate "record" for each computer with the same layout and fields.

-bd

Investigate the statement Status (CurrentUserName): it may give an help to identify different layouts or different soft. installed on each PC.

Put the result of this stat. in each record containing the info for each user (machine) and use it (via relation or search) to discriminate the information in the way you need.

Regards.

[ June 05, 2001: Message edited by: JPaul ]

I need to create a checklist of software for all the computers plus a box to describe errors/problems, if such take place. The list of software for all the classrooms is the same (Photoshop, Premiere, etc.), the only thing that is different is the name of the computers. There are 10 computers per classroom, and for each classroom I have to create a separate layout within a single database to make it easier to navigate between them. I was trying to avoid creating feilds for every piece of software in every machine. Instead I created a set of fields for one of the layouts and then copied it into the next one. However, it turned out that if I input information into the fields in one of the layouts, it shows up on the other one, as well. Is there a way to overcome this?

Thanx a lot.

Luka

It is not clear to me still, what you are trying to accomplish. However, you might consider a database file that contains one RECORD for each computer. That file would have one field for each of the following items or pieces of data: Computer ID, Location/Room, Model, Memory, HD Space, and any other information that you want to track that is specific to that computer and rather non changing. Then in a seperate file (a related "many" file of a one to many relationship) keep track of the software installed on each computer. This second file would have fields such as: Computer ID, Software Name, Version, Date Installed, Serial/License Number, and any other information particular to that specific piece of software. This is will create the database files. Into these files you add one RECORD per computer or per piece of software. you do not need to have a new LAYOUT for each computer or each piece of software. I hope this help and is not more confusing that it needs to be. Good luck.

[ June 05, 2001: Message edited by: RSGC ]

quote:

---

Originally posted by LukaSt:

I need to create a checklist of software for all the computers plus a box to describe errors/problems, if such take place. The list of software for all the classrooms is the same (Photoshop, Premiere, etc.), the only thing that is different is the name of the computers. There are 10 computers per classroom, and for each classroom I have to create a separate layout within a single database to make it easier to navigate between them. I was trying to avoid creating feilds for every piece of software in every machine. Instead I created a set of fields for one of the layouts and then copied it into the next one. However, it turned out that if I input information into the fields in one of the layouts, it shows up on the other one, as well. Is there a way to overcome this?

Thanx a lot.

Luka

---

I'm making a DB for my school, and it has to contain several layouts with identical fields in them (names of spftware). The only difference between the layouts is the names of the computers the software is installed at. Is there an economical way to reuse fields for software from one layout in the other ones? (The only thing I can think of right now is creating new fields for each layout and giving them slightly different names so that the computer can differentiate them from each other)

Thanks a lot,

Luka