Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM SQL » View Thread |
Messages 1 to 5 of 5 total |
Having trouble with an Insert query and a memo |
Tue, Apr 28 2009 1:23 AM | Permanent Link |
"Paul Coshott" | Hi All,
can anyone tell me whats wrong with the following query. It is created dynamically and the code used to add the memo bit is : Add(' ' + Engine.QuotedSQLStr(eNotes.Lines.Text) + ')'); The query is as follows : Insert Into Patients (PatientID, Surname, FirstName, Address1, Address2, Town, PostCode, State, PhoneHome, PhoneWork, Mobile, DateOfBirth, PatientType, EMail, Mailout, Notes) Values (13, 'Green', 'Fred', '44 Trewon Rd', '', 'Busselton', '6280', 'WA', '08 9754 1189', '08 9752 1148', '0401 254 789', '1962-05-15', 'CAR', 'fgreen@westnet.com.au', 0, 'Line 1') The error I'm getting is : DBISAM Engine Error # 11949 DQL parsing error - Exprecting NULL, Memo, Graphic, or BLOB expression but instead found 'Line 1' in INSERT SQL statement at line 34, column 5. If there is more than 1 line in the memo it comes thru as : 'Line 1'+#13+''+#10+'Line 2') Is this ok? Thanks, Paul |
Wed, Apr 29 2009 2:27 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Paul,
<< The error I'm getting is : DBISAM Engine Error # 11949 DQL parsing error - Exprecting NULL, Memo, Graphic, or BLOB expression but instead found 'Line 1' in INSERT SQL statement at line 34, column 5. If there is more than 1 line in the memo it comes thru as : 'Line 1'+#13+''+#10+'Line 2') Is this ok? >> Yes, that should be okay. Is the SQL that you are showing the actual SQL that is present in the TDBISAMQuery before the execution ? I'm missing something here, because everything you're showing looks fine. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, May 4 2009 12:38 AM | Permanent Link |
"Paul Coshott" | Hi Tim,
yes, the sql query in the question comes directly out of the sql property after it has been built at run time. I can't see what could be wrong. Cheers, Paul "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:57CBD755-8A52-42E7-9D2A-8951CC4D7571@news.elevatesoft.com... > Paul, > > << The error I'm getting is : > > DBISAM Engine Error # 11949 DQL parsing error - Exprecting NULL, Memo, > Graphic, or BLOB expression but instead found 'Line 1' in INSERT SQL > statement at line 34, column 5. > > If there is more than 1 line in the memo it comes thru as : > > 'Line 1'+#13+''+#10+'Line 2') > > Is this ok? >> > > Yes, that should be okay. Is the SQL that you are showing the actual SQL > that is present in the TDBISAMQuery before the execution ? I'm missing > something here, because everything you're showing looks fine. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Mon, May 4 2009 4:02 AM | Permanent Link |
"Paul Coshott" | Hi Tim,
just to give you some more information, the sql is going into a TDBISAMUpdateSQL. I am definately using the InsertSQL property and running the query using ExecSQL(ukInsert); Cheers, Paul "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:57CBD755-8A52-42E7-9D2A-8951CC4D7571@news.elevatesoft.com... > Paul, > > << The error I'm getting is : > > DBISAM Engine Error # 11949 DQL parsing error - Exprecting NULL, Memo, > Graphic, or BLOB expression but instead found 'Line 1' in INSERT SQL > statement at line 34, column 5. > > If there is more than 1 line in the memo it comes thru as : > > 'Line 1'+#13+''+#10+'Line 2') > > Is this ok? >> > > Yes, that should be okay. Is the SQL that you are showing the actual SQL > that is present in the TDBISAMQuery before the execution ? I'm missing > something here, because everything you're showing looks fine. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Wed, May 6 2009 11:48 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Paul,
<< just to give you some more information, the sql is going into a TDBISAMUpdateSQL. I am definately using the InsertSQL property and running the query using ExecSQL(ukInsert); >> Could you distill the problem down to a sample project that reproduces it ? If so, please send it to me via email and I'll take a look. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, May 7, 2024 at 06:25 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |