M
mcnewsxp
i have to create access form that mimic survey forms that contain lots of
questions and therefore lots of fields.
these are usully toss-aways and only used for short periods of time, then
when they serve their purpose they are deleted. the end-users usually want
their data as flat as can be. i like to use table binding because i don't
have to code any IO.
what are some of you doing do deal with this situation? for example, my
latest one will need mimic a two page form. each will have over 200 fields.
NOTE: any talk of re-usability and data normalization will fall on deaf
ears. the only reason we're using ms access for these applications is for
it's quick-and-dirtynesss.
so i'm just looking for some quick-and-dirty tips.
thanks much,
mc
questions and therefore lots of fields.
these are usully toss-aways and only used for short periods of time, then
when they serve their purpose they are deleted. the end-users usually want
their data as flat as can be. i like to use table binding because i don't
have to code any IO.
what are some of you doing do deal with this situation? for example, my
latest one will need mimic a two page form. each will have over 200 fields.
NOTE: any talk of re-usability and data normalization will fall on deaf
ears. the only reason we're using ms access for these applications is for
it's quick-and-dirtynesss.
so i'm just looking for some quick-and-dirty tips.
thanks much,
mc