I think it will max out around 35-40 entries.

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.

Perhaps as high as 100, but unlikely.

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.

I am out of my depth, but I am wondering if there's some other architecture that you could use- like passing in an array. There are too many entries to consider multiple properties.



Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

Hey,

No array features in SQL 2000; who knows about 2k5.

Brian

SQL Server 2005 will make available the .NET CLR and its datatypes, so arrays will be available. This would hardly be standard SQL, and the timing for SQL Server 2005 is still a bit out in the future, so you may want to evaluate whether this is a viable solution for you.

You might try the following for an alternative way to handle the situation you outline:

http://p2p.wrox.com/topic.asp?TOPIC_ID=2091

It's anybody's guess as to whether this is an efficient solution for you.

Jeff Mason
Custom Apps, Inc.
www.custom-apps.com