I never said you were wrong Joe and I don't expect that to happen anytime soon... but you need to lighten up today.  I know you're one of the Gods...

Ya that happens... a no error statement that really is an error .  That's why debugging was invented.

Oh, I think it means that you are doing something like this :

Select @MyVar = min(MyCol), MyCol2 from...

You cannot mix opening a dataset and setting variables at the same...

Nice to see you in a good mood today Joe.

Joking aside, have to agree with his thinking.  You need to know what you are doing and not just go blindly selecting...

6000 + posts and now I have to start all over again with sql 2005 .  Hopefully I have a headstart this time

No error in that code that I can spot... What error are you getting?

You usually create a staging table where you import the data.  Then you insert the "valid" records with something like this :

Insert into dbo.RealTable (Key, Col1, Col2) Select Key,...

You can do something like this :

if ...

exec dbo.Proc1

else

exec dbo.Proc2

...

That'll always return a single recordset and it's the server that controls what has to be executed... which is a...

If access is only showing the data, there's a way to make this work.  However access cannot execute this code without sql server.

I had many good teachers on that matter after school. But none better than yours truly .

"Good to hear from you again, Mr. Smarty-pants!  "

I wasn't studying stupidity at school... maybe I should have taken some extras

I was refferring to this from Farrell's post : case characters).  I imagine someone can refine this...

I used to always change his bulldozer approach to a set based solution.  However...

I hope you were not thinking about me... my numbers table is retired for the moment... Looks like you'll have to think about the other solution on your own this...

use

DbName

Select

* from sys.sysfiles where right(filename