... righto, i was just thinking about this the other day but i may have a small problem... my accounts are located in the front end ... in a seperate database on each individual clients computer while the backend with all the data is being hosted through server... my point is, if a user were to create an account in their front end... it would only be in their front end, not in any of the other clients...

Anyone want to maybe possibly... PLEASE,.... tell me how to fix this?

.. also though this part isnt exactly relevent to this part of the forum i dont want to post twice... what happens if the backend connection drops out while the front end remains open?

Cheers, for the help

How are you protecting the "back end" data? Seems like the accounts should be located there instead.

.. yeh and id put them there... i really would.... but then how am i to allow account generation?

I don't know how your business operates, so it's hard to say.

In some situations, the I.S. Staff might create the accounts. In others, the H.R. staff might. But in any case, account creation can be scripted if the users are assigned a privilege set within a User table.

ok... righto, heres how its setup... everything is done through the front end, back end has no gui whatsoever...the account restrictions in the front end are covered by layouts.. its enough... the backend is restricted by one different password pretty much only for me... anyway, the point is... though my accounts table is in my backend... the only way i can seem to create an account creation script is by executing it right there... only referring to the current files accounts...

i have no idea how i can create accounts in the backend from the frontend... its a pain and i should have thought about it before i started but the idea of a client side gui thrilled me..

thanks for any suggestions..

genx

oh right, by I.S. i assume you mean info systems or support... not really... what are H.R staff?

the way ive got it set out... people with adminsitration accounts .. there are a couple in the office trained in the program a little more in depth then others... but they are still simpletons and will never be given access to filemaker native account thingo...

Cheers

Your "simpletons" (I'm sure they'd love to hear you call them that,) need not have access to the Account & Privileges settings. You can use the account management script steps to add accounts, delete accounts, and change passwords in the interface file, the data file, or both. You might search the forums, as I seem to recall past discussions about this.

I.S. = Informations Systems. Same as I.T.. Presumably someone (maybe you) goes into the database to fix problems once in a while. In some environments, the I.S. Staff is also the ones who manage the accounts.

H.R. = Human Resources. Since they deal with comings and goings of Employees anyway, giving them the ability to add and delete accounts is not too hard (and can be tied in with other processes they might use if they are already entering stuff into a Personnel database.)

In most cases, it would be a bad idea to have users create their own accounts. It'd be too easy to cause mischief in such a system. An exception being where users only have access to edit their own records.

no no ... the accountsw adding section is in an admin section... restricted completly to admin staff... how does one enable scripting creation of an account in one file from another?... ill have a look through the forums for it anyway...

no no ... the accountsw adding section is in an admin section... restricted completly to admin staff.

So your admin staff has to add the user account on each computer? What a pain.

how does one enable scripting creation of an account in one file from another?

Same way as you'd script anything else in one file from another. Perform Script [ external... ]

oh right... woops, awesome, cheers

genx

... no but thank god this solution wasnt running yet... the previous one currently running is a single file and i havent had to much experience with split file solutions so yeh... i only just thought about that the other day...

Anyway, its all good, cheers for help