I've been looking into this a bit closer.

You might be able to solve this using a view as FACT table and/or as the Dimension table for currencies.

For the FACT...

Found one for the 92 version:

http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt

You can use a cursor and the 'WHERE CURRENT OF' clause in your update.

You can use either the SET or SELECT syntax. Both have their (dis)advantages.

SET @Name1 = Month1

SET @Name2 = 535.46

or

SELECT @Name1=Month1, @Name2=535.46

The...

Ryan,

In my opinion there is no reason at all to not replace NULLs in your fact table by references to a 'N/A' record.

I can see your management's point if you're...

You could add a 'Not Defined' value to your currency table and update all 'NULL' values in the fact table to point to this one.

I guess this is about the...

Frank,

Congratulations.

Seems odd to me that you still have some spare time, looking at the number of posts you have

Should be no problem.

.Net offers a number of wizards for creating Web Services, but there is nothing to keep you from writing the front for a Web Service in ASP....

Try

UPDATE TableA SET

Field1 = tableB.Anotherfield1,

Field2 = tableB.Anotherfield2,

...

FROM

tableB

WHERE tableB.ID = 1 

For the first problem.

Creating 'linked' tables should work. The procedures might be more efficient since the SQL server engine is more powerful. However, you do introduce network overhead, so this...

Agree with David. You cannot do this using just the foreign key relationships. The table layout with the TestOrg and Person tables having a FK relationship to the Address table...

You can create jobs using Enterprise manager. Go to your server->Management->SQL Server Agent->Jobs.

You can add a new job. It acts much like any scheduler kind of stuff. You can set...

You could add everything to a Job and start that from Access. I'm not sure under what security context a job runs if you start it manually.

You could use triggers without any problem. But you have to take care that they are fired upon EVERY insert or update you do.

So if the load of the queries...

There is no 'order of records' in a relational database. Even if SQL Server does apply some rules concerning the way in which the data is returned (in order of...