I think this has nothing to do with data, its settings in MTS which is causing the probs.Check u'r Component security. Disable the checkbox for Enable authorization and try it again.
If u dont break compatibility u can expand them in the existing interface but if u want a new expanded one (which breaks compatibility) then u will have to create a new abstract interface defn and again implement in the class where u want.
If u implement MTS code with Security context you can? Or else u can pass from the client the Machine name as a parameter. Sorry I don't think I can do much...
Its logical that ODBC will not save the password since its your app which should pass the password for security validation. The initial ask is just to test for connectivity.
create procedure sp_GetEmployeeDetails
@Eno int,
@Eno int output,
@EName Varchar(30) output,
@Sal Decimal(12,2) output
as
select @Eno=eno, @Ename=ename, @Sal=sal from emp where eno=@Eno
return
Just check for syntax as I have not run this in sql.
create procedure sp_GetEmployeeDetails
@Eno int,
@Eno int output,
@EName Varchar(30) output,
@Sal Decimal(12,2) output,
as
select @Eno=eno, @Ename=ename, @Sal=sal from emp where eno=@Eno
return
Just check for syntax as I have not run this in sql.
U cant make updates into the inserted table.I can just give a idea of creating a unique column in the exiting table or create a temp tab with unique val and go with the updates with the table directly.I have'nt checked the following modified query, but just work on it.
CREATE TRIGGER...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.