I was just trying to point out a real world scenario.  If I offended you I'm sorry.  That was not the intent.  The intent was to show that what you...

OK.. Dumb question here:

Why in this good earth would you want to knowingly install sp's 1st and create the columns later???  This is asking for HUGE problems.....

Someone or something could...

Why not save the MS Word doc as a text file and open with notepad, wordpad, textpad, etc..???

This will have the same information that QA likes and will avoid the...

I don't think that SQL is OLE compliant with Office components i.e. having Access dynamically update itself because the Excel spreadsheet changed or vice versa.

What you could do is run...

Try putting GO statements between each of the requests

CREATE DATABASE [Chapel Attendance]

GO

USE [Chapel Attendance]

GO

CREATE TABLE attendancerecord(StudentID CHAR (6) NOT NULL

Date TIMESTAMP NOT NULL)

GO

This might work...

Why does it have to be in the front?

If you are looking at creating some sort of ID column or other information you can just ensure that in your SELECT...

Sukhoi,

The ORDER BY is in both SELECTS already.  The code will work by removing the 1st only ONLY 

There are a whole bunch of different ways of doing this... Here are 2 simple ones:  Both rely on the VB app tacking on the % to the company name...

I tend to agree with most of the people here with my approach to debugging:

1. Print statements, or a variations thereof
2. Taking apart the sp and running each part separately and comparing...

what you could do is....

When you build the string either in the stored procedure that you are calling from VB or from the query you are building in VB ...

WHERE...

I was curious.  A lot of questions are mis-posted....

remove the order by from the 1st SELECT statement and you should be good to go...

Laurence,

What reporting tool are you using??

Unfortunately, that wouldn't work.  Regardless of where the user really is in the world the SQL SERVER thinks that they are physically sitting in front of it touching it's physical keyboard

In the copy sql server objects task object UNCHECK "use default options"

UNCHECK the top 3 options (security area).

This may be all you need..