Messages
Reply
Edit
Delete
The _screen object is not restored so you have to redo those entries every time the form is refreshed. You can do that in the method (forgot the name and cannot look now) of the form. However it is faster it seems to set the properties into a form property that will automatically get refreshed by FiC.
Since FiC does not yet save the _svcreen object, there is no real VFP way to manager user or session info unless you attach it to every form and keep refreshing it. Thatb refrehsing can be recalling the values from somewhere in the form pre-refresh of every form or using the WWC session object to set/getsessionvar.
We have a wrapper prg that if we ar on the web it uses setsessionvar and on LAN it uses screen. That way when FiC supports _screen we mage a 1 line change to the wrapper.
I'am in France.. so no significant difference between our times..
It's time to work..
This is not the WEB user ID, but I store a user ID has own application .. Moreover, in the _SCREEN properties I stores others informations (user profile, user right, etc. ..)
Hoping to have given a satisfactory answer ..
Regards
GLS
Hi GLS.
The first thing I have to say is - TIME YOU WENT TO BED! lol
(Assuming the West Wind call log time is local to yourself)
It is 11:54 in UK, so I'll know what time zones are displayed when I
look at my message on the board.
As I said in an earlier message, very new to FIC so I may be talking
out of my rear passage.
Is the problem that the User ID you store is the Web login ID, which
not Michele's User ID from her(?) logon data table? Hopefully all will be
solved when the 'WAIT WINDOW' results come back from Michelle.
Keith
Hi Keith,
for each use of a form, F.I.C restore the user in the INIT() of the form.
this is the reason why i put my UserId in a _screen property with the two fonctions of awserver.prg
* ------------------PROTECTEDPROCEDURE wUserSetLPARAMETERS ; twUser,; && Identifiant utilisateur && /!\ type variable tlTemp && [.F.] Identité d'emprunt_Screen.AddProperty('myUserId', m.twUser)DoDefault(m.twUser, m.tlTemp) && {fr} Toujours conserver cette instruction ! - {en} Always keep this instruction!* ------------------PROTECTEDFUNCTION wUserGetLPARAMETERS tlTemp && [.F.] Retourner l'identité d'emprunt RETURN_SCREEN._myUserId
Regards
GLS
Hi Michele.
In that case I have no idea as I also have no idea how FIC handles
different instances of the same form. I have not yet got to
the stage where I can test FIC as a web app to see if I get similar
results, but it would seem very unlikely the FIC developers would
not have noticed such a problem.
As suggested by others, are you sure in the form INIT the User ID
is correct? Try adding a WAIT WINDOW TRANSFORM(UserID) or similar
at the point you collect user data to visibly see what is happening.
Keith
No problems in desktop
Hi Michele.
Does the same problem occur when your application is run as a desktop?
I have one form where are shown some objects depending on the active user's appointment. The first time this form is shown there are no particularly problems; when i open the same form on another device for another user, the first time the form is shown i see the same objects of the last user......How can i set my form to start every time with active user's objects ?
Thanks
