If you have over 100 fields in your table... your table design is
Thank you for pointing that our John, I am sure there are many things wrong
with my design but it works for now and that is what is important at this
point.
I've needed as many as 60 fields in a table... once, about twelve
years ago, in Oracle. I've never *needed* more than 30 in Access.
OK.
Take a look at the normalization of your table. Is it not possible
that you have some one-to-many relationships embedded in each record?
I suppose, but I don't know what that means. What I am doing is keeping
track of individual purchases, employee time, customer, work done, dates
work is done, hours, machines work is done on, figuring some of this into
formula's that tell me certain things about all of this and relating all of
that to a job # assigned to the work. It is rather complicated to begin
with and all of the information needs to be on one screen for different
employees to assess and address. Soooo..., I want to put already existing
fields onto a window that can be scrolled though.
That would be nice, instead of being told of how incompetent I am with
Access. I already know my ignorance that is why I came here. But thanks
for your reply.
Ted