User Record Count

[redballoon]

I would like to get the number of records a user has made, so this can be displayed, then I would like to create a function to add 1 to this number so that the next record created would be individually numbered.

Then when the user logs in they will see, a total of the records they have made and then when they click back and forth they will see the records numbered...

Any help given most greatfuly appreciated,

Thanks...

[bcooney]

If you have a UserCreatedID in each record, then you can just count them. Do you have a user table, each with a unique UserID?

You could display "their" records in a portal on the User Form view using a relationship by UserID=UserCreatedI.

[redballoon]

Yes I do have a user field with a unique ID.

Do you know is it possible to create a list of al users ?

Since you ahve a create user button surely it is possible to view all users ?

[sbg2]

Might I suggest a find when the user logs in as per attached file?

Three users:

Account: Admin

User: Admin

Pass: Admin

Account: Gary

User: Gary

Pass: Gary

Account: John

User: John

Pass: John

You can see the shortcomings of not using autoincrementing serial numbers in the post: http://www.fmforums.com/forum/showtopic.php?tid/191695/post/273995/#273995

MyFile.zip

[bcooney]

You've provided the next step in the process, thanks.

Also, the UserCreatedID is an AutoEntered calc field equal to $$CurrentUserID that is set in an Open Script.

[comment]

Why not use a relationship from the user table to 'find' the records?

Also, the UserCreatedID is an AutoEntered calc field equal to $$CurrentUserID that is set in an Open Script.

What's the point in setting a variable to something that is always available as a function?

[bcooney]

How is the UserCreatedID available as a function, comment?

I don't use Created User name entry option, if that's what your referring to. Names change.

I was trying to build functionality a bit at a time in this post, to avoid totally overwhelming the OP. I was going to suggest a portal of records on the User Form with a gtrr button, or a gtrr button that takes the user to a list view. As usual, we're guessing here bcs we don't have much detail. All they asked for was a count.

Edited January 14, 2008 by Guest
elaborated

[comment]

How is the UserCreatedID available as a function, comment?

It's not. I'm afraid I misread your post and thought you were referring to account name - since that seems to me the natural choice. So the question is why use userID instead.

[bcooney]

Because Account Names can change, too. I do use Get(AccountName) to find in the Users table on startup and then store the $$UserID.

[comment]

Account Names can change, too.

Perhaps, but how often does that happen? I'd prefer to use the straightforward method for everyday use, and deal with the change if and when it comes.

[bcooney]

I politely disagree. Women marry, for example, and wish their account name changed, perhaps. If a critical feature of the system is to see how many records this user created (telemarketer perhaps) then relying on account name is undependable.

[comment]

LOL, what year do you have? I'd sooner believe a woman wanting her account name changed because she got divorced...

Anyway, what I am trying to say is this: changing an account name is not an everyday event. It requires either a skillful administrator, or a carefully prepared script. Both could change the account name on existing records on the same occasion*. I don't see why everyday operations should be made more complex in preparation for this eventuality.

---

(*) or add the previous account name to a list in users table

Edited January 14, 2008 by Guest