Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM SQL » View Thread |
Messages 11 to 16 of 16 total |
Insert from Memory Table into Physical Table |
Tue, Apr 18 2006 11:20 AM | Permanent Link |
"Allan Roberts" | "Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:E0D28569-D793-4DB9-A0A1-F1F28EC3548F@news.elevatesoft.com... > Allan > > > I think what Tim's referring to is the fact that "Description" doesn't occur at all in your sql statement as shown so where is it coming from? The obvious conclusion is that either the sql you posted isn't the one giving the error, or you haven't posted all of the statement. > > I think (and Tim will correct me if wrong) that Description is a reserved word so you'd need to enclose it in quotes wherever it is. > > Roy Lambert I posted the entire code and the only code that is associated with the entire DBIsamQuery. Again, please note that any previous SQL statements were cleared immediately before adding the statement that I posted. Description may well be a reserved word, but as you can see, it is not included in my SQL statement. That is why I am wondering if the parser is tripping over the Description column in my table (even though I have not explicitly mentioned it in my query). Of course, in that case, I have no opportunity to enclose it in quotes. Thanks for the reply. |
Tue, Apr 18 2006 11:56 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Allan,
<< I'm not sure what you mean; There is only one SQL statement-- the one that I posted. I'm not sure how another could be available to mix since I cleared any previous statements immediately before SQL.Add: >> Sorry about that, you are correct. I've had a cold the last few days and the darn cold medicine is making me a bit loopy. The problem is that the columns in the source table do not match those in which you're inserting the data, specifically the Description column doesn't match properly. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Apr 18 2006 12:03 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
But in an earlier post Allan said "Purchase and Purchase1 are of identical structure." Roy Lambert |
Wed, Apr 19 2006 8:13 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< But in an earlier post Allan said "Purchase and Purchase1 are of identical structure." >> Well, if that's the case then I'll need to see the table structure to see what is going on because it isn't something obvious. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Apr 19 2006 7:47 PM | Permanent Link |
"Allan Roberts" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:8BF3FED4-4B78-46E4-A7F0-CA0DD8B9220A@news.elevatesoft.com... > Roy, > > << But in an earlier post Allan said "Purchase and Purchase1 are of > identical structure." >> > > Well, if that's the case then I'll need to see the table structure to see > what is going on because it isn't something obvious. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > Here's an update: Although the structures are identical, I wondered if there was something different that I wasn't seeing. I tried an experiment--I performed a repair on the physical table, and now it works! There was no specific message about what was repaired--just the usual "Table Repaired" message followed by the "started at..etc." message. Who knows what it was, but I'll take it. Thanks for all of the responses. |
Thu, Apr 20 2006 5:41 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Allan,
<< Here's an update: Although the structures are identical, I wondered if there was something different that I wasn't seeing. I tried an experiment--I performed a repair on the physical table, and now it works! There was no specific message about what was repaired--just the usual "Table Repaired" message followed by the "started at..etc." message. Who knows what it was, but I'll take it. Thanks for all of the responses. >> Um, the repair fixed the problem, but the repair process didn't indicate that anything was wrong with the table structure ? That doesn't sound right at all. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, May 23, 2024 at 07:54 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |