Re: ODBC Access?

[rob@xxxxxxxxx]

Another possible solution would have been to journal the file. Journalling 
is not the AntiChrist. 
See:
CRTJRNRCV
CRTJRN
STRJRNPF
May be more steps to set up than simply overriding the odbc source. 
However may have some nice long term payback.

There's even a data area that you can create in a library that says that 
any new files created in this library will automatically be journalled. 
Forget what it is though.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





daparnin@xxxxxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/02/2004 02:40 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: ODBC Access?










Yahoo!!!  It worked!!!  You da man, Steve!  :)  I'll have to file that one
away for future reference.  I probably never would have figured it out on
my own.  You gotta love those detailed error messages that you get. Thanks
again.


Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx





  
                      Steve Landess  
                      <sjl_abc@hotmail.        To:       Midrange Systems 
Technical Discussion 
                      com> <midrange-l@xxxxxxxxxxxx>@SMTP@CTB   
                                               cc:       David A 
Parnin/Topeka/NISCO/SPCO@SPCO 
                      12/02/2004 02:21         Subject:  Re: ODBC Access?  
 
                      PM  
  
  



Dave -
You need to change your ODBC data source.

It is trying to use commitment control,
which expects the file to be journaled.

This is what probably what SQL7008 is indicating.

Go into Administrative Tools > Data Sources (ODBC),
click on the Server tab, then click the Advanced button
at the bottom of the panel.  On the next panel, in the Commit mode:
drop-down box, select "Commit immediate (*NONE)" and
click Ok.

This should fix your problem, given that none of the text fields
in your Access database are longer than the corresponding
fields in the AS/400 file.

Regards,
Steve

----- Original Message -----
From: <>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, December 02, 2004 12:50 PM
Subject: Re: ODBC Access?


>
>
>
>
> Steve,
>
> Thanks.  That was a good idea.  I ran a query on the Access table to
check
> all of the fields for null values.  There were a couple of records with
> nulls and I assigned values to them.  There are now no nulls.
> Unfortunately, it still does not work.  I still get the original error
but
> now I also get a dialogue box that reads:
>
>  [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL7008 - EXTRACT in DPLIB 
not
> valid for operation. (# - 7008)
>
> There are ten fields in the table that are all text.  There are ten
fields
> in the DB2 file that are also all text with the same field lengths.  I
may
> have to try a different approach.
>
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
>
>
>
>
>
>                       Steve Landess
>                       <sjl_abc@hotmail.        To:       Midrange 
Systems
Technical Discussion
>                       com>
<midrange-l@xxxxxxxxxxxx>@SMTP@CTB
>                                                cc:       David A
Parnin/Topeka/NISCO/SPCO@SPCO
>                       12/02/2004 11:39         Subject:  Re: ODBC 
Access?
>                       AM
>
>
>
>
>
> Dave -
>
> Do you have any columns in the Access table containing null values?
> If the corresponding fields in the AS/400 file don't allow nulls,
> you will encounter this error.
>
> I had a similar problem when uploading data from an Access table,
> and I wrote a VB function that I used in my Select statement
> within the Access database to substitute blanks for nulls in alpha 
fields
> and zeros for nulls in numeric fields.
>
> Steve
>
> ----- Original Message -----
> From: <>
> To: <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, December 02, 2004 10:04 AM
> Subject: ODBC Access?
>
>
> >
> >
> >
> >
> > Can anybody tell me what I need to change on the iSeries to accept an
> ODBC
> > upload from a MS-Access database?  I can open the file in Access as a
> > link-table but if I try to add to it I get a message that reads
> > "ODBC--insert on linked table 'DPLIB_EXTRACT' failed.
> >
> > This is a one-shot project so in the interest of security anything 
that
> > turn on I can turn off once it's done.  Thanks.
> >
> > Dave Parnin
> > Nishikawa Standard Company
> > Topeka, IN  46571
> > daparnin@xxxxxxxxxxxxxxxxxx
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.