Having trouble visualizing how to create a login

[June7]

Just took another look at the DLookups. They are all wrong syntax, except for the first one that populates the password textbox. Review Access Help on DLookup.

[seth.murphine]

Just took another look at the DLookups. They are all wrong syntax, except for the first one that populates the password textbox. Review Access Help on DLookup.

Didn't want to leave you hanging, thinking that I just ran off.

I have since found a different way of doing this and am about finished. Just having an issue at this point with with the change password form, but I'll get through it.

I have another question though regarding queries, maybe I should start another thread in the Queries section.

I know you can show totals in a query (sums,counts,averages, etc), but what I want to be able to do is take the queried totals and put it into its own table.

So for example Bob has 8 records that total up $30 total revenue, 8 total calls and Sue has 20 records that total up $50 total revenue and 20 total calls it will create a separate record in the new table for Sue and Bob with just their totals. Is this possible and how would I do it?

[June7]

It is possible but why bother? So much easier just to query the aggregate calcs when needed. It is also contrary to relational database convention to save aggregate calc data. The risk of data getting 'out of sync' is a concern.

[seth.murphine]

I guess I'm just over thinking it, as long as the users can pull reports for certain date ranges within that query. I just felt that it would be better or more of a positive reinforcement to so that each user could see on a form their progress for the day. Also so that when pulling performance reports I know the hard data is there to pull from rather then calculated data. Also for the fact I have already been keeping that type of information in the older database (I didn't create it), and that older data needs to be maintained in the form of totals. For that I guess I could just throw the table in there and put another report button for 'legacy' information.

I have to say my brain is fried from working on this think for the last couple of weeks, I'm at the point that normal stuff is looking foreign and I'm unable to think around obstacles... its getting aggravating.

[June7]

I wouldn't worry much about how data used to be managed and just focus on how it will be managed now. When we upgraded our database we didn't set it up exactly same as the old. I even left the old data in the original dBase tables and set up links. If a need arises to incorporate old and new data in same output, I find a way.