What is wrong with using a dashboard

[Lou_Reed]

In the forum I have seen many responses to posts claiming to avoid using
a dashboard. My question is why?

It seems a logical and useful way to organize things, but apparently
not.



I am certainly not looking for validation on using a dashboard, but I just need to know
what is wrong with them.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[pbaldy]

Are you talking about the table-based built-in dashboard? I don't use them, but there's nothing wrong with them. I find them too limiting, but there are very good developers that use them.

[Lou_Reed]

I am not sure what I am talking about since I have just started using them, dashboards. It is just whenever I put any question about dashboards in a post it usually comes back with an answer, but a warning that one should not use dashboards. They are simply a thing of the past. Not needed anymore.

Respectfully

Lou Reed

[pbaldy]

Well, perhaps follow up on one of those and ask the person why. Some people would call a "main menu" form a dashboard, since it may have charts or other information "at-a-glance" for the user. Others are thinking of the built-in dashboard, which probably is a thing of the past. I guess you need to define what you/they mean by a dashboard form.

[June7]

They may be thinking of the old Switchboard Manager form wizard, which was also commonly called a 'dashboard'. I have never used it, don't like. Probably a good reason MS pushed it to the background and no longer automatically shows on the form design tab. It's still available (as of Access2010), just have to hunt for it.

Otherwise, I consider any form used as a 'menu' to be a dashboard, whether it uses macros, VBA, or the Switchboard structure.