1 username per database in the Virtual Airline?

[AltairZQ]

As I see it, only 1 user is necessary per database, that's 1 user for all the VA members, otherwise you'd need to create them one by one in
FsPadmin and maintain them, that would too much added work I think.

Am I right or there is something else I'm missing?

One thing is we won't be able to query by "flights_UserName", but we can query by "flights_PilotName", and in case the VA member has a different pilot
name in FsP and the VA (or more than one pilot in FsP), we could modify FsPgetflight and assign to flights_PilotName the VA pilot name.

Does this sound right?

[Drew]

depends on the VA

you can do it eitherway.

eg, world tour im doing, the VA config file is the same for everyone, however, atlantic sun i have a personalised va config file

[AltairZQ]

Thanks again Drew.

If it's not asking too much, I'd be very interested in knowing the reasons that made you use a personalised file for the "atlantic sun".

[Drew]

sorry it wasnt my choice, it was just the file i got send after i registered with there VA

[AltairZQ]

Ok... hope I don't get off on the wrong foot...

Thanks

[Andreas Jatridis]

AltairZQ wrote:
I'd be very interested in knowing the reasons that made you use a personalised file for the "atlantic sun".

The reason for the personalised config-file is that we fully integrated FSP into our existing roster/pirep system. We have a rank-structure that allows our pilots to fly only those flights (or
planes) they are qualified for, and to check this, we need to know their pilot-id (and password) when they file a pirep with FSP. At first we only slightly modified the admin-script that
allowed us to add their pilot-id to the FSP user database, but after reaching 150 FSP users, I decided to rewrite some of the FSP scripts because the workload got too high, because
whenever a pilot joined or moved from one hub to another, I had to change his info in the FSP database. Now they only need to download an already modified "standard" config-file and
enter their personal info (which they can change whenever they move hubs). No need to use the FSP admin anymore

[AltairZQ]

Thanks a lot Andreas, that was very helpful, never thought about making a script that added the user to the users table (that is what I guess you do).