Some questions about VS2008 web pages, Gao Feng asks for answers

1. When registering, let it verify in the database to determine whether the user's registered account is duplicated, or add a button to the back of the account, and let the user click the button to detect whether the user's account has been registered.

2. The administrator should log in in the background, do not log in from the front desk, the identity of the visitor is set in your personal setting, if you set up no account can also be accessed, it is to allow visitors to access, and the same is true for making comments, the administrator is logged in from the background, and the function of adding comments to the administrator is that, the background deletion of comments will add a statement to delete comments in the database, and it is not difficult to update the comment page in time, so you can let it reload the page (reload data from the database) It's going to refresh automatically.

Hope it solves your problem, ask for a recommendation.

Fields in the database: loginid (login), pwd (password), group (the group to which the person belongs, 1 administrator and 0 common users).

1—When submitting the registration, query the database to determine whether the loginid already exists, and if it exists, prompts, it does not exist, then execute the insert statement.

2—Add a linkbutton after each comment, text="Delete"，commandname=delete。When a user logs in, determine the group to which the user belongs, if the group is 1, the linkbutton will be displayed, otherwise it will be hidden.

I would like to say the registration page.

1. Whether it has been registered.

If you know how to use ajax, you are using ajax, if not, you will first query the user table in the database according to the user name you entered to see if you can find it, if there is a prompt to change the user name, otherwise submit.

2. Permissions. Add a column to the appropriate table in the database to distinguish whether you're an administrator or a guest.

After logging in, the administrator saves his permissions in the session and then verifies where the permissions need to be verified (add a verification at the beginning of the ** page to see if the value of the session is empty, whether there are corresponding permissions, if it passes, then perform the following operations, otherwise a prompt page will be returned).

The problem of the two people on the top floor is basically solved.

In fact**Run is not required vs2008,**The operation can be independent, as long as you support the language of the **program you use, it's OK!

Generally, the generation ** is the default path when it is created!

I don't know if that's clear to you?

Is your friend a newbie? Hmm,It's recommended to take a screenshot of the full screen.,Look at the troubleshooting tips.,Or copy it.。。。 Hmm,You try to correct it yourself.,See if it's a typo and don't write a semicolon Those low-level mistakes.,If not,You can find the wrong place through the number of lines in the troubleshooting prompt.,Check it.。。。

Well, the order is wrong.

It should be a problem with the database connection, you can send it down to see and debug it.

Probably the database is not connected.