Using Session Variables to Pull Specific Data

[vinyltap]

I have been all over the forum and help and I must be missing it.

I have created a session variable (session.User_Name) which is actually a user's email address.

How do I get it so certain pages (grids) pull only information pertaining to that User.

I can log in and go to those pages but I see all users not just the one logged in.

Any assistance would be wonderful.

[Steve Wood]

You place the filter in the A5W page. It would look like this:

tmpl_tr_mygrid = a5w_load_component("tr_mygrid")
with tmpl_tr_mygrid
	componentName = "tr_mygrid"
	DBF.filter = "user_name = \""+session.User_Name + chr(34) 
end with

or

tmpl_tr_mygrid = a5w_load_component("tr_mygrid")
with tmpl_tr_mygrid
	componentName = "tr_mygrid"
	DBF.filter = "user_name = " + quote(session.User_Name)
end with

Assuming user_name was your table's field for the email address and mygrid was your grid component.

Just create the A5W page and insert the grid component, you will find a section like below where you can insert your filter.

tmpl_tr_mygrid = a5w_load_component("tr_mygrid")
with tmpl_tr_mygrid
	componentName = "tr_mygrid"
end with

[vinyltap]

thanks again

I did see that in my research and I didn't realize I could just type that line in. Worked fine.

thanks as always.

ken

[vinyltap]

I'm not totally out of the water I guess

After it was working earlier I now get an Invalid Username or Password when I attempt to log on (from all log on points) which means there should be an error in my Validate Code but it looks right. I am using a correct username and password.

if (session.User_Name = "") .or. (Password = "") then

currentform.has_error = .t.

currentform.error_message = "User name or password is blank."

else

dim correct_password as C

correct_password = lookup("[PathAlias.ADB_Path]\members", "Email="+quote(session.User_Name), "password")

if (correct_password <> password) then

currentform.has_error = .t.

currentform.error_message = "Invalid user name or password."

end if

end if

Is there something missing or wrong?

[peteconway]

Your session is timing out

include the
<%a5
a5w_include("logintest.a5w")
%>

in your new a5w file.

[Steve Wood]

Ken,

I think Peter was responding to your earlier post about building your A5W page and including the logintest there. It will not affect the problem you are having in your login dialog (Invalid User name...). Can't guarantee this is it, but throw an alltrim() around your password variables, as in:

if (alltrim(correct_password) <> alltrim(password))

[vinyltap]

Still getting error

Tried the Alltrim but still get the error message. I don't see how it could work then not. I tried changing the session.User_Name back to just User_Name but the system points to that as an error.

I also tried multiple username/passwords and they all failed.

Any suggestions?

[Steve Wood]

You're going to have to figure out if you are getting a value in your lookup (and other variables). Test the same in an A5W page like this:

session.user_name = "myemail"
? lookup("[PathAlias.ADB_Path]\members", "Email="+quote(session.User_Name), "password")

plublished and preceeded by a question mark so you can see the results of the lookup (should be your email address).

[vinyltap]

Where to Place

Do I put that in the Validate Code for the login in lieu of my current lookup or is it code by itself? I did the first and got the same Invalid error.

[Steve Wood]

All I'm saying is find some way to determine what you are getting back from your lookup, and to a lesser extent, the rest of your variables. It is pretty likely your variable Password contains what you expect since it comes directly from the dialog. but the lookup is suspect because, well you don't know for sure what it is returning. Bottom line is that your correct_password and password don't match, so the lookup is suspect.

A way to determine what the lookup returns is to run an A5W page. You would put in exactly what I posted:

session.user_name = "myemail"
? lookup("[PathAlias.ADB_Path]\members", "Email="+quote(session.User_Name), "password")

..where myemail is a known valid email address in your members database.

[vinyltap]

Results

I created a a5w page that had only that code. Published it and then went to open it. I got a blank page- does that mean it is finding no password when the lookup runs?

[Steve Wood]

Yes, either the email is not found, or it does not have a value in the password field. Now, I know you probably have proper values in all fields. But it gets you closer, even if more perplexed! BTW, try going to the table and run Utilties / Pack to reindex and clean up the table, if that is a problem. To test the path, try temporarily renaming your members table, and run the A5 page. If there is NO error, then your alias is pointing to some other copy of your tables.

etc.

[peteconway]

List the entire *.a5w file so I can have a look.

Steve my point about the

<%a5
a5w_include("logintest.a5w")
%>

Was that if the session times out, the DBF.filter = "user_name = \""+session.User_Name + chr(34) will fail. So he needs to keep checking for it.

Also paste the actual error - it will help. Just to make certain of the problem.

[vinyltap]

Still Occurring, Here's what I tried...

Looked at case sensitivity- didn't matter. Then I downloaded the data from the web to match up with my local dbase and they match perfectly (but I noticed the field names on some fields were shortened- not the "password" field though- cause to worry or is that standard?).

I entered on the web a new member from the web and was able to login fine. Went to try old member login- got the "Invalid User Name or Password". Is there something that could happen if I upload new data. It seems it works ok if I add in members from the web but once I download and then re-publish it all goes kablooky.

[vinyltap]

I Think I know the problem- help to fix

My login issue is definitely due to uploading a table with data. When I upload my members.dbf the login doesn't work. When I manually enter in the same exact member info the login works, but it brings me to another issue. It appears that my members.dbf field rules don't upload as well. (BTW I am using Alpha 5's publishing).

Any of this make sense?