Viewing 9 posts - 16 through 24 (of 24 total)
What do you mean by ODBC calling?
In my case everything has to happen on the server...
🙂
March 31, 2003 at 10:23 pm
Func1 works just fine.
I've simulated the trigger from Query Analyzer (removed the first line "create trigger etc." and replaced the "from deleted" and "from inserted" part with a select statement)...
🙂
March 31, 2003 at 9:23 am
Try this and you'll get an answer for start:
select text
from sysobjects t1
left join syscomments t2 on t1.id = t2.id
where t1.name = 'sp_MS_marksystemobject'
PS: I don't know more about this...
🙂
March 31, 2003 at 8:54 am
I don't know if it will help, but try to modify the "T5.ProdType IN ('Release', 'Update', 'Upgrade')
" part to a JOIN. With other words: put the 'Release' and 'Upgrade' values...
🙂
March 31, 2003 at 8:44 am
Here is the trigger:
-- trigger start
CREATE TRIGGER Trig1 ON dbo.Tabel1
FOR INSERT, UPDATE, DELETE
AS
--return
-- comment1
declare @date smalldatetime, @first smalldatetime
set @date = dbo.func1('param') -- comment
-- comment...
🙂
March 31, 2003 at 8:16 am
Hi everybody!
First of all, my apologies, especially for Antares686, who wrote (and I did not pay enough atention):
"May be that something about the datatypes is causing the issue. For example...
🙂
December 12, 2002 at 12:47 am
The whole story is the following:
I am using MS Access XP .adp and MS SQL Server 2000 to realise my project. This means that if I modify an SQL object's...
🙂
December 5, 2002 at 1:09 am
What is DDL?
"For example if one is CHAR(2) and the other is CHAR(4) then in the other every items has 2 spaces after it so 'X1 ' would not be...
🙂
December 4, 2002 at 6:08 am
Dear Antares686!
Your advice did not fix the problem. The symptom is the same with the new syntax, too.
But, I'll keep in mind your advice.
🙂
December 3, 2002 at 11:50 pm
Viewing 9 posts - 16 through 24 (of 24 total)