Hi all
I am trying to work out why my TDAT demo cannot 'see' my VC++6 installation (for use in Stored Procedure compilation).
As far as I can tell, VC++6 was installed in very standard way, so I can't think why the SP compilation process would fail to find it.
Assuming that some registry key is used to determine the presence/absence of VC++6, does anyone know what key it is?
Failing this, is there a technote (or similar) describing the prerequisites / requirements for SP compiliation to work?
Wishing I had a debugging switch...
Many thanks
James
I am trying to work out why my TDAT demo cannot 'see' my VC++6 installation (for use in Stored Procedure compilation).
As far as I can tell, VC++6 was installed in very standard way, so I can't think why the SP compilation process would fail to find it.
Assuming that some registry key is used to determine the presence/absence of VC++6, does anyone know what key it is?
Failing this, is there a technote (or similar) describing the prerequisites / requirements for SP compiliation to work?
Wishing I had a debugging switch...
Many thanks
James