Hello all! I am looking for an opinion from anyone who has one. I use FileMaker to track our Fixed Asset Inventory. When I first took over the task, the equipment we had disposed of lived with all of the active equipment. Someone higher above me made the decision that the disposed files should be in a totally separate file (this person has limited to no knowledge of FileMaker). Because of accounting needs we need to keep track of all the equipment regardless of active rotation or disposal. I think it would be better to have all of this information together but in separate tables. In your opinion which would be the better option regarding functionality? Please let me know if you need any more information. Thank you in advance for any help.

Sharon

You haven't provided any reason why all the equipment shouldn't be in the same table. You could simply mark disposed equipment, preferably by entering a date into a DateDisposed field.

The owner doesn't want to have to see the disposed pieces if he is looking at the database. I offered to set up scripts for him but he wants to search for (example) all of the Fast & Furious Super Bikes that we have and only see active pieces. He doesn't want to have to press any "extra" keys to see the info he wants or look at different screens.

We have location codes that mark disposal pieces and there are also fields that show the disposal date, price and other information. He just wants it to be easier for him. He is not very experienced with computers.

Well, you could have "satellite" tables that "filter" by status. That is, two new tables that are sub-types of equipment. All that's in these tables are the foreign EquipIDs. Search for "Graham Method" posts by Fenton. This'll give him separate list views without needing to find, and yet keep all Equipment in one table.

The owner doesn't want to have to see the disposed pieces

He is right about what he wants - not about how he wants it. You could simply take away his privilege to view those records (and to show all records) or rig his finds to always include an extra request.

How about make a button and attaching a script that takes him into search mode and pauses so he can specify his criteria. Then once the search is performed the found set is constrained to omit all records where not IsEmpty(DateDisposed). Or something along those lines maybe.