Yes it is much easier to use and IDENTITY but, based on this discussion, you can't.  The SequenceNum must be based on a match to the Request_ID.   It's a reasonable...

The report rowsource would be 'SELECT * FROM CHIL0708A1'.  Why would you want ADO to also build a report?  It would be MUCH more difficult using ADO to create a formatted...

I thought that was what a hyperlink was; data which functions as a logical link to address internal or external documment locations.  The field type in the table is a...

This type of problem is not unusual in a production development environment.  I try the easiest test first which is simply copying the form, renaming the old form, and then renaming...

It's true.  Access has a hyperlink data type which is a bona fide hyperlink, not merely a string.  I suspect the driver that converted the data type has to at...

I use ADO in VBA quite a lot to execute and return OUTPUT values.  From your original post it appears you need to execute the adodb.command.  You DO NOT need...

I believe you may have a couple problems.  The first would be thatyour local computer configuration, SQL Server SP1, is badly outdated.  Service pack 3 should be your bare minimum...

I'm not sure why posts are assigning the value of the case statement to depressed but it is simply an alias.  The SQL below in more in line with assigning...

Is your object only to change lower case characters to upper case?  You don't need to know where those characters exist, just use the UPPER sql command.  Of course it...

All data types are int.  I've temporarily patched this problem with and IF NOT EXISTS(SELECT * FROM @tmpView WHERE ID=@BlockEnd) and then I insert the ID number.  I hate...

I've upgraded a number of Microsoft Applications that were dependent on DAO/MDAC libraries and have experieced the least pain by upgrading the libraries during the process.  If you could change your...

Try creating a primary key by adding a field called ID as an integer and then make it an IDENTITY field with a seed of (1, 1).  Set it as...

Nothing.  I stayed with it until solved.  It works fine now.

I have the dates updating in QA now and I'm working on getting the correct dates.  Thanks for your interest.

I use the following proc that originally came from 4GuysFromRolla but modified it from isql to osql.

ALTER procedure dbo.xOutputToFile

(

@sServer varchar(30),

@sDB varchar(30),

@sUser varchar(30),

@sPWD varchar(30),

@sOutFile varchar(255),

@sSQL varchar(1000)

)

as

--From 4GuysFrom Rolla

--Demonstrate how to...