In Access, a combo box with this statement is attempting to navigate to a particular record by synchronizing the form with the underlying recordset.  There is an Access combo box...

The SHIFT-return thing also works in many word processors including Microsoft Word.

In my experience, the file you're restoring FROM has to be on the same server as the database you're restoring.  SQL restore only "sees" what is on its own box.

Thanks, Steve, but could you give a bit more detail?  Where am I setting this DSN-less connection?  And how?  As I said before, we don't want to manually redirect hundreds...

To run the code described in the previous posts, does the user have to have administrative rights to their machine?

A bit of extra information:  we're running SQL 2000 on Windows 2000 and will be migrating to Windows 2003.

Zoul:  Just a suggestion: if you use named parameters in VB you're less likely to miss a comma.  Example:

.Parameters.Append .CreateParameter(name:="@Site", type:=adInteger, direction:=adParamInput, value:=gintSite)

Here's a snippet of a function I wrote to strip out any non-alpha characters from a name, such as apostrophes and hyphens.  You can add a third criterion to the...

Question:  if I set up a job to run sp_updatestats, will this significantly impact performance of my server or network?  I'm scheduling the job to run at 2 am when...

We had major memory leak problems with SQL 7, but they magically went away when we upgraded to SQL 2K.

Dana

Dhoffman@CharterOak.edu

Hit submit too soon ... disregard previous entry.

Regarding your statement:  "Unless issueing the rollback/committ stops the proc ... " - doesn't it?  I've always assumed that once you rollback, that's...

Regarding your statement:  "Unless issueing the rollback/committ stops the proc ... " - doesn't it?  I've always assumed that once you rollback, that's the end of it. Note my...

Since you're going to roll back if any errors happen, you don't need an error variable:

insert statement ....

If @@ERROR <> 0

       ROLLBACK    ---no need to go further!

update statement ....

If...

Just a minor point ... I've found that when testing a field for a number of values, the IN function is more manageable and easier to read than a series of OR...

How about this:

EMPLOYEE TABLE

EmpID (primary key)

LName

FName

TeamID ... foreign key to Team Table

TEAM TABLE

TeamID (primary key)

TeamName

DivisionID ... foreign ID to Division Table

DIVISION TABLE

DivisionID (primary key)

DivisionName

ChannelID ... foreign key to Channel Table

CHANNEL...