Bob_Hansen wrote on Nov 29
th, 2006 at 7:47pm:
If the subform table view is not wide enough to show all the fields, how about making two or more different subforms, one above the other, or each on separate tabs, each with its own group of fields? You can control the widths and positions and visibility on the sub form designs.
Problem then will be how to keep the multiple sub form views in synch so when looking at top/bottom form the other one is showing the same record? May need some type of routine that would sort all views when changing lines ..... hmmm, this is getting complex....
"Complex" huh?

I find myself thinking the same thing somewhat. The more I do with this program, the more I want to do. This was intended to be a fairly simple merging of two databases, with a couple of expectations:
One: To insure that when we added repair data that the serial numbers were accurate-eliminate those silly one digit "off" things that happened occasionally when we were using two seperatate dtatbases in Q&A.
Two: To be able to view repair and inventory dta for each individual pice of equipment at the same time. We have a "policy" that we developed a few years back in which we decided not to put $1500 worth of repairs into a $200 piece of equipment

Being able to see the repair data when viewing inventory would be very cool. As a matter of fact, it is cool-extremely so.
So that's it in a nutshell, so to speak. I have NO doubts that Sesame will exceed our needs and expectations. We have a few hurdles to clear, but the fact that I work with the poster children for short-term memory loss will not squash my optimism.