Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
comp.sys.ibm.as400.misc
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
ODBC double quote problem
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bob  
View profile  
 More options Dec 30 2011, 1:41 pm
Newsgroups: comp.sys.ibm.as400.misc
From: Bob <rwen...@baystatesoftware.com>
Date: Fri, 30 Dec 2011 10:41:49 -0800 (PST)
Local: Fri, Dec 30 2011 1:41 pm
Subject: ODBC double quote problem
Print | Individual message | Show original | Report this message | Find messages by this author
Hi all,

   Got some Excel data trying to upload to the iSeries.  I import it
into MS Access and then use ODBC/append query to upload to the
iSeries.  1906 rows are successfully inserted into the iSeries table.
Most of the rows have double quotes (") embedded in a text field
(table contains product that is sized by inch), but 6 rows return
special characters (3-F or 3-7 in hex caused by 2" 4" 8" in string).
I used create table on the iSeries and standard Client Access ODBC.
Want the data transferred "as is" with no special characters or
delimiters.
What am I missing ??

Thanks
Bob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jonathan Ball  
View profile  
 More options Dec 30 2011, 1:48 pm
Newsgroups: comp.sys.ibm.as400.misc
From: Jonathan Ball <jonbal...@gmail.com>
Date: Fri, 30 Dec 2011 10:48:38 -0800
Local: Fri, Dec 30 2011 1:48 pm
Subject: Re: ODBC double quote problem
Print | Individual message | Show original | Report this message | Find messages by this author
On 12/30/2011 10:41 AM, Bob wrote:

> Hi all,

>     Got some Excel data trying to upload to the iSeries.  I import it
> into MS Access and then use ODBC/append query to upload to the
> iSeries.  1906 rows are successfully inserted into the iSeries table.
> Most of the rows have double quotes (") embedded in a text field
> (table contains product that is sized by inch), but 6 rows return
> special characters (3-F or 3-7 in hex caused by 2" 4" 8" in string).
> I used create table on the iSeries and standard Client Access ODBC.
> Want the data transferred "as is" with no special characters or
> delimiters.
> What am I missing ??

> Thanks
> Bob

Why the two step upload?  Why not just upload directly from Excel using
the IBM i Access plug-in?

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Bob  
View profile  
 More options Jan 4, 9:32 am
Newsgroups: comp.sys.ibm.as400.misc
From: Bob <rwen...@baystatesoftware.com>
Date: Wed, 4 Jan 2012 06:32:37 -0800 (PST)
Local: Wed, Jan 4 2012 9:32 am
Subject: Re: ODBC double quote problem
Print | Individual message | Show original | Report this message | Find messages by this author
Thanks for the reply Jonathan.
Looks like I was incorrect.  The MS Access table that is loading an
ODBC linked iSeries table is the result of SQL Server data (ODBC link)
from the outsourced company website.     Sorry for any confusion.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jonathan Bailey  
View profile  
 More options Jan 6, 6:24 am
Newsgroups: comp.sys.ibm.as400.misc
From: Jonathan Bailey <jonathan.bai...@tesco.net>
Date: Fri, 6 Jan 2012 03:24:44 -0800 (PST)
Local: Fri, Jan 6 2012 6:24 am
Subject: Re: ODBC double quote problem
Print | Individual message | Show original | Report this message | Find messages by this author
On Dec 30 2011, 6:41 pm, Bob <rwen...@baystatesoftware.com> wrote:

> Hi all,

>    Got some Excel data trying to upload to the iSeries.  I import it
> into MS Access and then use ODBC/append query to upload to the
> iSeries.  1906 rows are successfully inserted into the iSeries table.
> Most of the rows have double quotes (") embedded in a text field
> (table contains product that is sized by inch), but 6 rows return
> special characters (3-F or 3-7 in hex caused by 2" 4" 8" in string).
> I used create table on the iSeries and standard Client Access ODBC.
> Want the data transferred "as is" with no special characters or
> delimiters.
> What am I missing ??

> Thanks
> Bob

Are these really just double quotes or have they become 'smart'
quotes, which curve in on each other? MS Word has a tendancy to
generate these sort of quotes.

Jonathan.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Bob  
View profile  
 More options Jan 11, 8:51 am
Newsgroups: comp.sys.ibm.as400.misc
From: Bob <rwen...@baystatesoftware.com>
Date: Wed, 11 Jan 2012 05:51:23 -0800 (PST)
Local: Wed, Jan 11 2012 8:51 am
Subject: Re: ODBC double quote problem
Print | Individual message | Show original | Report this message | Find messages by this author

> Are these really just double quotes or have they become 'smart'
> quotes, which curve in on each other? MS Word has a tendancy to
> generate these sort of quotes.

> Jonathan.

Curly quotes was the problem.  After reviewing curly quotes and
straight quotes
in MS Word I went back to the SQL Server data source and sure enough,
there they were.  You really have to look to see the difference, but
that was it.

Thanks for everyone's help.
Bob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google