I think it was one of "those" problems with sep. I had already tried refreshing the sep. Then, I recompiled the program and forgot about the debugger. When I called the procedure from strsql, it seemed to lock - it was the rdp debugger taking control! How is that possible? When I refreshed the sep, it didn't catch the call. If I recompile, I should be obliged to refresh the sep! N'est-ce pas!!
De : wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] De la part de
Envoyé : jeudi 2 décembre 2010 14:55
À : wdsci-l@xxxxxxxxxxxx
Objet : Re: [WDSCI-L] Stored procedures
Check the user ID the SEP was set up to use and the user ID
you are running the SQL under. If they don't match I think
the SEP is ignored.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.