Hi Gerard,

Nothing silly about it.  Even thought you may come across an Integer PK which is not auto incremented by the database, but you are right.  That was a code I wrote fast without testing for Terry, but was corrected in the following messages.

Edhy Rijo

Hi Edhy.

This might sound like a silly question but I 'Asumed' that a primary key field in SQL 'had' to be unique and you could not have duplicates ?. This must'nt be the case if you have written a routine to validate it ?? 

Yeap you are now in the right track, so go for it.  Also for your current BO all you need to do is change the Inherits to your new base BO, the same thing applies to forms and other controls.

Edhy Rijo

So let me get this straight. 

Hi Terry,

Yes, there are some sample code in the forums, probably Ivan (the Google expert) may provide some links, but basically this what you have to do:

1. Create a BO class and do not map it to any of your tables.  You could name it whatever you want, I name mine "ApplicationBaseBusinessClass.vb"
2. Add all the custom, generic code you expect to use in all your BOs like the ones I posted here.  Also if you use some custom field properties in all your BO with the same name, here is a good place to have them all.
3. In your current and new BO, change the "Inherits" statement from:

     Inherits MicroFour.StrataFrame.Business.BusinessLayer
to
     Inherits CardTrackingSystem.Business.ApplicationBaseBusinessClass

Of course in the sample above the namespace "CardTrackingSystem" should be replace with your own NameSpace.  After that, recompile your project and start having fun with your base BO class.

Edhy Rijo

Is there some where I can find a basic subclass of the BO that has Everything that is needed to make it work so I can start adding some of these functions and not have to do it on Every BO?

Hi Charles,

I have not worked with a TVP yet.  I have a consultant "Uri Dimant" which is a MS SQL MVP which helps me with those deep needs and even though he is pretty good explaining this type of things with MS-SQL, sometimes I don't have the luxury to pay to much of attention to details.  He has created some complex stored procedures to deal with millions of records and re-factored those couple of times to take advantage of new functionality of MS-SQL 2008 R2.  In case you or anyone needs serious help with any MS-SQL problem, feel free to contact him.

Edhy Rijo

Hi Terry,

I've been there, done that! Welcome to the club

Glad you find it useful.

Edhy Rijo

I think your idea of an array for multiple fields is very good, especially in keeping the function as generic as possible.

Just as an aside :  I've been working a lot with using table value parameters in stored procedures and I'm really interested to find that unlike other type of params, you don't need to account for *not* passing the param - the TVP in the sproc will just be an empty table.  Interesting in that you can write where clauses in the sproc that let you receive either a single or TVP param for comparison and it will work depending on what you pass in. 

( reading that over it probably doesn't make any sense unless you've been playing with TVPs but for anybody who has, the TVP as empty table if no param is passed came as a surprise to me and somebody may find it useful )

I did find the Primary Key problem and I was able to change that but now with All of the Great Ideas I will be looking to change almost all of my fill routines.