Hi Nadya,

I wrote a long message but it did not post. I got a white page saying the site could not be found. When I looked over at my cable modem, I noticed the lights were not blinking which mean I have lost my connection to Cox Communications. I tried to get back to my message so I could copy it, but could not get back. The message was lost. This will remind me one more time to save may messages before posting. I'm currently coming in over my backup hayes modem.

A shorter message this time because its been a long day and is 10:54. Time for bed.

Be sure that your data is normalized. Define parent child tables and build restraints from the child's foreign key into the parent's primary key. This will ensure referential integrity. Also, be sure each record has a unique key. You can use MSSQL auto-increment for this. The unique key in the child table is not a primary key, but a key that would allow the deletion of a singel record for example.

Stored procedures are nothing more that queries copied into the database. If you have a difficult query that is use often, someone discovered it would be benefical to copy it into the database container. Then when it was need, it could be call without a need to continually recreate it. Since having a query hard coded into an app provides the same benefit of negating the need to continually recreate a query from a command window or MSSQL management console, much of the benefit of SP is eliminated. However, it you want to try SP, create a query in the MS SQL console. When you have it working like you want, copy it into the database container and give it a meaningful name. A meaningful name is important when the number of SP increase to five or six hundred. You can check the MSSQL doc for syntax of how to call the SP from asp.

LelandJ