I haven't got one to hand but it's all in the sysindexes table. Probably wouldn't take long to write one.

"Whats the weather like up there in sunny Aberystwyth?"

Sunny of course (amazingly enough I'm not being sarcastic either).

Do you want to send me your list of dates and I'll try...

Hi

Just to narrow the prob down a bit:

Have you tried with a few hardcoded values e.g.

select cast(convert(char(100),'1980-03-22',101) as datetime) as [Date]

Are the dates in the two different DBs all...

Hi dec

At first glance I'd say drop the extra 'Select' remove the 'As NextRev'

SELECT @RetVal= MAX(RevNo) + 1

FROM dbo.tblRevision

GROUP BY DocumentID

HAVING (DocumentID = @DocumentID)

And give that a try.

To account...

Sorry, my reply was a bit lazy. Text field is a CLOB.

In SQL Server 2005 there is an XML data type but I suppose that's not going to help...

Hi Naren

I'd suggest either using CLOBs (character large objects) or reading up about "select for XML" which may or may not be appropriate for your needs.

All the best

Bit late in the day to be adding another point but I thought I'd best mention the use of variables in your trigger.

You're selecting idPackage into a variable from...

Good old Microsoft. They always provide a tick box for any problems you're having. I'm still looking for the tick box in the .Net development environment that tells it to...

I assume you're talking about .Net. I have no idea why it forces you to create a new connection for each new data adapter created in the visual designer. But...

Do you mean that when calling @@IDENTITY in the script that inserts into Package in the first place you get idObject?

If so then you need to use Scope_Identity(). This will...

I might be jumping the gun a bit but I'm pretty sure that you're out of luck. However, if there is such a feature do let me know because I'm...

Liliana's is a good solution too as long as Ron is sure he's never going to duplicate ID's between the Standard and Custom tables. If he does, then Standard table's...

Of course the correct answer is, no matter how you actually write the query, to lay it out in a readable way so that the poor bugger who has to...

Sorry you wanted to join Orders so that would actually be:

select

*

from

vw_Items vi Join Orders od On vi.ItemID = od.ItemID

to return you everything from orders and the other two...

At first I was thinking maybe a case statement, but now I'm leaning towards using a View e.g.

Create View vw_Items As

Select

*

From

Standard, Custom

Then you can:

select *...