Derek Stone

Use the onunload and onbeforeunload events.

You get what you pay for, which with WebMatrix, is a rather course toilet tissue. You can get a better constructed product in a public restroom.

Simply put, I think they look like crap.

Menu items all have Name properties. Look at the Properties Window.

http://www.divil.co.uk/net/controls/sanddock/

Please don't dig up old threads. Start a new one if the topic's last reply is more than a few weeks old.

You'll need to use an array of type SqlParameter[]. SqlParameterCollection does not expose a public constructor. By using an array over which you can enumerate, you can add the parameters one by one. This is an ugly method of doing it, but there aren't many other decent options (e.g. reflection).

You'll need to attach your global.asax file and any classes from which it may inherit.

Please do not bump threads. Your post will be removed if it continues.

That's your opinion. If you like poorly designed projects and an HTML editor that alters input, then Visual Studio .NET is the way to go. If you don't like those "features", it is not. Of course a lot of this is fixed in Visual Studio .NET 2005 ("Whidbey"). +1 Notepad. +1 XMLSpy. +1 SlickEdit. -∞ Visual Studio .NET 2002/2003.

Microsoft SQL Server, which I can only assume you're using, offers a timestamp data type. You can use this data type to detect and account for changes in records, and increase support for concurrent users, which as far as I can tell, is your greatest concern. You seem to question the method you're currently using, and you're very much justified. Using view state in that manor is a poor choice, nevermind with that much data. The best approach to this is to determine if the project absolutely requires this level of functionality. The vast majority of applications do not require each and every update to be checked against the database for the sake of detecting recent changes made by other users. For those of us familiar with ADO and various other database libraries, we know that record locking can and will cause more problems than it will ever solve. I'm not claiming this is what you're trying to do, but history does apply here. By accounting for other concurrent users, the application is going to increase in its complexity. In short, ask yourself if you really need this. With that said, you'll find that a solution using timestamp columns and notifications to the UI will work quite well. If a user submits changes to a record, simply check the timestamp and prompt them to take further action. Those actions include viewing the current record, merging the records or disposing either the current record or their record. Again, these choices increase the complexity of your application's business logic and presentation layer (the changes to the database layer are actually rather minimal).

While you can't add child elements to option elements, you can set their style properties. <select> <option value="FF0000" style="background-color: #FF0000;">Red</option> <option value="FFFF00" style="background-color: #FFFF00;">Yellow</option> <option value="FF00FF" style="background-color: #FF00FF;">Purple</option> <option value="00FF00" style="background-color: #00FF00;">Green</option> <option value="0000FF" style="background-color: #0000FF;">Blue</option> </select>

You'll need to read up on impersonation.

You can't store a lone time value in a datetime field in a Microsoft SQL Server database. Period. As Robby mentioned quite clearly, you'll need to use some other method.

No, one doesn't need to know C/C++ (or any other language for that matter) to code in assembly. You can write assembly in any text editor. It's the same as any other language when it comes to authoring.

While I misread your code when I replied the last time, the code I posted still applies. What your code does now is create parameters that aren't attached to the command. You need to use the OleDbCommand.Parameters.Add() method to create the parameters. You can then assign the parameter values (or use the code I posted which does the same thing, but on one line). On a personal note, I fell victim to this very same problem when I first started using the System.Data.OleDb namespace. So don't feel bad. :)

As PlausiblyDamp mentioned, make sure that Windows Firewall is configured correctly. You'll need to unblock port 1433 (default) for the TCP and UDP protocols.

You add the parameters, but you don't assign the parameter values. command.Parameters.Add(@"socialsecuritynumber", OleDbType.VarWChar).Value = socialSecurityNumber;

I see it used quite frequently to format RSS feeds being displayed within the Web browser. Other uses: http://www.topxml.com/xsltstylesheets/default.asp

No, it won't work for Microsoft Access databases. The "architecture" is far too limited for something such as cache callbacks.

Have a look at the following code in the Web page: <script language="javascript"> <!-- function __doPostBack(eventTarget, eventArgument) { var theform = document.Form1; theform.__EVENTTARGET.value = eventTarget; theform.__EVENTARGUMENT.value = eventArgument; theform.submit(); } // --> </script> Perhaps that'll give you a hint as to what you're missing. :)

Your best bet is to store the connection string with a full path (not relative path) to the database in the application's configuration file (web.config).

IIS 5.1 comes with FrontPage 2000 Server Extensions. They're most likely installed as well. You can check by going to Start | Run | "appwiz.cpl" | Add/Remove Windows Components | Internet Information Services (IIS). You can upgrade the extensions if applicable on your system; do so from the Internet Information Services Management Console.

The feature you're looking for is in the next version of the .NET Framework, version 2.0, also known as "Whidbey". For today's applications a combination of triggers and extended stored procedures (XSP) does the trick quite nicely.

And even that is a bit of a stretch.