he he , I did now

..everything but the kitchen sink...

 I'm a bit rusty.

thanks bud,

yogi

cheers Kenneth

I definitely believe that it's better to encapsulate whenever possible. I'll include the trigger code, to see if that helps to clarify...

salut Remi,

thanks for the extra tip

a plus,

yogi

hiya,

well, they both work.Thanks.

yogi

Cheers Steve,

I've modified the schema a bit.

I am trying to store details about different companies.I can see an issue where I could potentially assign...

Thanks all.

I went for the access option at the minute, simply because I'm not yet confident enough that I can adequately control the permissions to my sprocs and tables.

cheers,

sweet as a nut.

Thanks to all.It's strange, but I initially didn't have a length specified for my @operator param, yet that part of it worked.

livin and learnin.

yawn...morning

I can now get the spoc to work with a hard-coded value of 10.

I am trying to pass in a param to replace the...

cheers Rax.

I'm out of the office now, but I'll try first thing tomorrow.

yogi

hi Steve,

I simplified my sproc.It will actually take 2 params:

1) the operator, ie "=" ">" or "<"

2) a date

Then, if i can get it to work, I can have...

hi Pat.

I'm using the sqlServer "identity" as the PK for my entities.

So essentially, If I create a new employee and do not assign to a company, then (if the "default" companyId...