I realize now I probably did a bad job of creating a narrow question 🙂

I ended up just going with

"what I've done so far is to add "EmployerId:<EmployerId>" to the...

Here's a script I whipped up that illustrates basically what I'm saying

use master

CREATE DATABASE FT_TEST

GO

use FT_TEST

GO

CREATE TABLE [dbo].[EmployeeFTS](

[EmployeeID] [int] NOT NULL,

[EmployerID] [int] NOT NULL,

[Names] [nvarchar](150) NOT NULL,

[PhoneNumbers] [nvarchar](max) NOT NULL,

[Address]...

I'm targeting an x86 installation of SQL Server on windows 2003 with an x86 build of the dll

I got a virtual machine of xp up and running and I've started...

Tonci Korsano (8/17/2010)

---

hi there,

maybe your assembly is supposed to go inside "program files (x86)" folder.

maybe you need to build that assembly project, with visual studio, to target x64 environment in...

it looks like it's some environment issue I'm running W7 64 bit

and it works fine to deploy for a colleague on W7 32bit

I set all the targets to x86 which...

Jonathan Kehayias (8/17/2010)

---

The other thing to check is:

Did you deploy both assemblies to the same database? It would be pretty easy to deploy one of them to a different...

Jonathan Kehayias (8/17/2010)

---

The other thing to check is:

Did you deploy both assemblies to the same database? It would be pretty easy to deploy one of them to a different...

no only WOG.SQL.SHARED dll shows up because

it's in there and...

bteraberry (5/7/2010)

---

Throw away whatever you read that said that. That is...

I have been listening this is all in the pursuit of knowledge

And no a colleague was suggesting the triggers and I was trying to find a solution that didn't involve...

bteraberry (5/7/2010)

---

Again, you're making this way harder than it needs to be. Using triggers to hard code the table when you can simply use the capabilities of T-SQL to...

Lowell (5/7/2010)

---

this is a logical mistake; you should never try to keep a counter in a table; the counter should be derived in a view, isntead; go with bteraberry's idea...

I don't think you're understanding the issue

Lets say I have some blocks these blocks come in 3 different colors

Each time I acquire a block that block has it's OWN unique...

Yea I'm sorry I did such a bad job of setting up the data structures and explaining the scenario

There's a Client table that has a unique incrementing clientID

There's a SITE...

Yea I figure someone was going to answer that I tried to explain it well but I guess I didn't or maybe there's some other identity I need

To quote myself...