RobertM said:
Hello Rick:
It's a simple two table database with a subform for entering daily
data. The parent record is a mutual fund # the child records are
dates realted to the parent. For example fund # 722A will have
$10,000 entered for March 2nd, 4,000 entered for march 3rd and so on.
There are going to be about 50 parent records which I beleive is
reason alone not to go with tabs, but that's what he wants.
If you actually mean 50 parent records, you will have several problems.
The first is what happens when you get to 51,
The second is in identifying the individual record in the "tab" and the
third is in not really being able to use a tabbed form
Forms basically show a single record at a time.
You could place tabs or buttons to fake tabs on a single form/subform(?) and
click event would do what the combo or list box would do. Move to a
particular record.
With the combo it's a bit of code the wizard will write, with the tabs it's
1 - n modifications of such code.
I used to solve a lot of problems like this by explaining the difference in
development time then asking for a written description of what was wanted
and asking the magic question. "What is my budget for the project?"