Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Logging in to a web site!

Status
Not open for further replies.

jward

MIS
Dec 21, 2000
57
US
I'm developing a web site with VB.NET, I want to create a login similar to what is used here on Tek-Tips. When the user is NOT logged in there is a login on the form, when the user is logged in the form updates and they have access to more features. I have 1 page that has all the controls on it, depending on what the user does controls visiblility is changed. I will be storing the user account information in a Access database. What would be the best way to do this, session variables, cookies, web.config ? Pointer to some good tutorials on the subject would be good as well
 
OH GOOD GOD, do you HAVE to use access?!

Access + anything that isn't a small office app = TROUBLE!
(bad experiences)

Anyway, that aside:
The easiest thing would be to stick all the controls (whether logged in or not) into the "login area". THen, in your code, you set up some way to check if someone is logged in or not. If they are, show the stuff for being logged in and visible = false for the other stuff. If they aren't logged in, show the login controls, and visible = false to the other things.

You shouldn't have too much trouble with it.
:)

Jack
 
Instead of Access, why don't you use MSDE? It's the SQL Database engine, powerful and of great practice for when you switch to SQL Server. MSDE should be free for download, I believe, with the .NET Framework SDK. In anycase you can find it at
ps. >OH GOOD GOD, do you HAVE to use access?!
Jack, YOU ARE HILARIOUS!!! Daren J. Lahey
Just another computer guy...
 
At this point I'm being Cheap, I'm not sure what kind of traffic to expect. So until I know i'm getting the hits I don't want to pay the extra for SQL access. I do have the
Login working but I'm not sure whats the best way to deal with users that logged in. Some input I've been hearing from ASP.NET programmers is that session variables is not the way to go? Where would be the best place to store this?
 
cookies. That's what I would use. That's what this site uses.
Daren J. Lahey
Just another computer guy...
 
I agree with Daren. For the login, cookies would be the way to go. That way you can log the user back in even if their session expires.

As for the ACCESS thing, Daren did mention that MSDE is FREE. That'l do donkey, that'l do
[bravo] Mark
 
MSDE, is there any way to test if its installed on a remote server? or I have it on my developement machine but I'm not sure if it's on my ISP's.
 
you install it on YOUR machine. It's a development tool.
MSDE stands for Microsoft Desktop Engine.

once you have it installed you can access to it through the server explorer of the VS.NET

hth Daren J. Lahey
Just another computer guy...
 
It's unlikely that it is by default. You would have to contact your ISP and ask them. Another option is MYSQL which is also free I believe and there are quite a few ISP's I have seen that have it listed in their feature list. That'l do donkey, that'l do
[bravo] Mark
 
MSDE would be your best bet if you didn't want to pay for sql server, but still wanted the best option for scalability.

If you start using Access now, what happens when you DO get heavy traffic and need to upgrade your database? Instead of holding alot of your code in code files, you'll want to transfer them to stored procs to get the performance and security boost, which means alot of new code being written potentially; all your code that connects to your access db will need to be changed to connect to the new data source; Access is notorious for easily becoming corrupted, meaning that if something buggers up, you better have a backup and be able to restore it quick, otherwise your site is going to have major down time.

I don't mean to preach to you what you should do, but the last place I worked at used Access as the main local database for their distributed POS application, and now they're really stuck because of performance issues, Access issues (corrupted databases happen ALOT), and the inability to really do anything new with their code.

So bottom line: PLAN FOR SCALABILITY! Access is great for small office apps to keep track of clients or something, but is HORRIBLE for web applications and web sites in general. If you don't want to bother with the MSDE, then look into Mark's thought on MySQL. MSDE would be the best I think though, and like Mark said: "It's FREE!"

Just my thoughts though,

Jack
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top