ct: RE: Access SQL Question
To: CF-Talk <[EMAIL PROTECTED]>
Or,
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
ALTER PROCEDURE dbo.upu_Instance_Delete
@InstanceID int
AS
-- Variables
DECLARE @lCurrentID int
DECLARE @lError
Or,
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
ALTER PROCEDURE dbo.upu_Instance_Delete
@InstanceID int
AS
-- Variables
DECLARE @lCurrentID int
DECLARE @lError int
DECLARE @lInstanceID int
DECLARE
Qasim Rasheed wrote:
> I want to recursively delete descendants at all levels. Any thoughts?
How about a self-referencing foreign key with ON DELETE CASCADE?
Jochem
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
[Donations and Support]
parent in (#parents#)
_
From: Qasim Rasheed [mailto:[EMAIL PROTECTED]
Sent: Thursday, 19 August 2004 3:09 p.m.
To: CF-Talk
Subject: Re: Access SQL Question
I want to
I want to recursively delete descendants at all levels. Any thoughts?
- Original Message -
From: Matthew Walker <[EMAIL PROTECTED]>
Date: Thu, 19 Aug 2004 10:25:19 +1200
Subject: RE: Access SQL Question
To: CF-Talk <[EMAIL PROTECTED]>
Is this what you want?
Is this what you want?
DELETE
FROM myTable
WHEREparent = 3
Or do you want to be able to recursively delete descendents (i.e. children,
cgrandchildren.) at all levels?
_
From: Qasim Rasheed [mailto:[EMAIL PROTECTED]
Sent: Thursday, 19 August 2004 8:32 a.m.
>I have a table that I transferred from Access to SQL and had a field
>setup as auto number. Now I am getting an error message when I try to
>submit new info to the table in SQL.
>
Yes You will need to go into SQL enterprise manager and make the col that was auto number in access to Identity y
Just wanted to say thanks - changed the field in Enterprise Manager.
Thank you!!!
Donna French
-Original Message-
From: G [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 18, 2004 1:37 PM
To: CF-Talk
Subject: Re: Access > SQL Question
SQL Server manages auto-incremented fie
SQL Server manages auto-incremented fields differently than Access does. I believe you have to go into SQL Server Enterprise Manager and modify that field in the table so that SQL Server knows it is an autonumber field.
- Original Message -
From: Donna French
To: CF-Talk
Sent: We
no problem...
-Original Message-
From: Tim Heald [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 9:08 AM
To: CF-Talk
Subject: RE: Access SQL Question :(
ohhh I thought it was around the field value.
You got it.
Thanks everyone
Tim
-Original Message-
From: Mark A
ohhh I thought it was around the field value.
You got it.
Thanks everyone
Tim
-Original Message-
From: Mark A. Kruger - CFG [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 10:05 AM
To: CF-Talk
Subject: RE: Access SQL Question :(
Tim,
AS has been mentioned, if you are
Tim,
AS has been mentioned, if you are creating a string and passing it to the
cfquery tag, make sure and use preserveSinglequotes( ) around it:
#preservesinglequotes(myQueryString)#
If you do not, the CF escapes the single quotes FOR you and you end up
with:
update printers set
what are the data types for the columns?
what version of access of are you using?
- Original Message -
From: "Tim Heald" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, August 01, 2003 9:52 AM
Subject: RE: Access SQL Question :(
query expression '''new make'''
But it runs fine in SQL view in access.
Weird
Tim
-Original Message-
From: Tim Heald [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 9:48 AM
To: CF-Talk
Subject: RE: Access SQL Question :(
The query you see is my ou
The query you see is my output from the variable I created containing the
SQL statement.
Man I hate access.
Tim
-Original Message-
From: Michael T. Tangorre [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 9:28 AM
To: CF-Talk
Subject: Re: Access SQL Question :(
can you show us
try to use [ ] in column names, like [MAKE], you can also partially delete
the sql statement one by one to find the bad row.
- Original Message -
From: "Tim Heald" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, August 01, 2003 4:19 PM
Subject: Access SQL Question :(
can you show us what the query looks like in the debug output? Wait, does CF
4.5 output that i forget. :-) If so, send that to the list. That would
let us see what the dynamic query looked like when it failed i think,
and we can go from there.
mike
- Original Message -
From:
Tim Heald wrote:
>
> [Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in
> query expression '''new make'''.
>
> Any Ideas? BTW, this is a dynamic script I am writing
PreserveSingleQuotes?
Jochem
~|
This one works fine in sql server, but you need to test it with ms access.
SELECT RIGHT(emailAddress, CHARINDEX('@', REVERSE(emailAddress))-1) AS
[domainName]
FROM dbo.customers
GROUP BY RIGHT(emailAddress, CHARINDEX('@', REVERSE(emailAddress))-1)
ORDER BY [domainName]
- Original Messag
843-357-1847
http://www.showstopperonline.com
-Original Message-
From: Jeff Chastain [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 11:19 AM
To: CF-Talk
Subject: RE: Access SQL Question - Round 2
No, that is along the lines of what I have been trying without any luck.
Okay, I
OTECTED]]
>Sent: Friday, January 17, 2003 11:19 AM
>To: CF-Talk
>Subject: RE: Access SQL Question - Round 2
>
>
>No, that is along the lines of what I have been trying without any luck.
>
>Okay, I have the following tables and data:
>
>table: issues (id, owner)
> 1
o:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 11:19 AM
To: CF-Talk
Subject: RE: Access SQL Question - Round 2
No, that is along the lines of what I have been trying without any luck.
Okay, I have the following tables and data:
table: issues (id, owner)
1 Doe
2 Klein, Doe
3 Jame
No, that is along the lines of what I have been trying without any luck.
Okay, I have the following tables and data:
table: issues (id, owner)
1 Doe
2 Klein, Doe
3 James
4 Doe, James
table: owners (name, email)
Doe [EMAIL PROTECTED]
James[EMAIL PROTECTED]
Klein[EMA
No access guru, (anymore:-/) but try
SELECT Firstinlist as (or "=" ???)left(issues.owner, inStr(issues.owner,
',')-1)
FROM issues, users
WHERE Firstinlist = users.name
Something like that...
WG
> -Original Message-
> From: Jeff Chastain [mailto:[EMAIL PROTECTED]]
> Sent: 17 January 200
24 matches
Mail list logo
