Lookup tables - VB Com development - lkuptbl.dll - Works on NT but not W2K or XP

Hi

Currently developing ASP / VB com projects on an NT workstation.
I use lkuptbl.dll for lookup tables used by the web sites (not heard of it before starting this job - chap I'm taking over from recons it is an MS dll. Can't find it on MS web site though).
I successfully run the vb dll project in design time on the NT workstation.
I compile and successfully deploy using a W2K pc.
I cannot run the vb dll project in design time on either W2K or XP...! (Even though it compiles just fine on W2K - haven't tried compiling on XP yet).

The problem is that Application.StaticObjects.Item("blah") is empty on W2K and XP. Works just fine on NT though. The object is defined in the global.asa.

Anyone know how I can rectify this?

Is there a different lkuptbl.dll version for W2K or XP ? I can't find one....
Is it perhaps some server setting peculiar to W2K and XP that isn't on NT that needs setting?

I'm very confused....

Cheers

I've not heard of this DLL before. Remember though, NT uses COM whilst W2k & XP use COM+. So there is every chance that the structure of any calls are slightly different.

Re-compiling under a 'COM+' operating system may do the trick.

Hi

Thanks for the reply.

I'm currently compiling under a com+ system - w2k pc - and then deploy it to customers using both nt4 and w2k servers and all is fine. Just can't run the dll from the ide on the w2k pc (or xp). Application.StaticObjects.Item("blah") is empty on both w2k and xp!!!

Cheers

Hi, did you ever get this to work on XP? I'm having the same problem and would greatly appreciate any help. Many thanks.

Hi

Unfortunately no - I'm still developing that product on a knackered old NT4 workstation :(

So far as I know it is someting to do with the 'user' that is running the dll in the vb ide versus the 'user' that is running the compiled com+ object on XP/W2K (ide fails in XP, but compiled works. Both compiled and ide work ok on NT4). I have been told by developers at my company with many more years experience than myself that there is no way around this and they all use NT4 too, but I can't believe that! There has to be a way around. There are some MS knowledge base articles skirting around this area that involve adding some registry stuff, but I have not been able to get any of it to work yet (and nearly killed my XP PC in the process!).

Sorry for the negative response. If you have any luck yourself, please let me know - I can't stand developing on NT4!

Cheers

My NT4 box died last week forcing me to look into this again. Didn't find a solution but do have a work around to get things working on my XP box.

During design time:

1) Search and replace in the vb dll source code all instances of Application.StaticObjects with Session.StaticObjects

2) Where these objects are declared in the global.asa change the scope to "Session" instead of "Application"

It'll now work in design time in the vb ide.

But, reverse these changes prior to deploying the app.

Too simple, why I didn;t think of this before.... If however anyone has found a real solution rather than the above work around do let me know.

Cheers

Just use ADO, and search tables that way. Make your own LOOKUP