fpODBC to SQL question

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-
> list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of
Fairlight
> Sent: Wednesday, January 20, 2010 1:40 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: fpODBC to SQL question
> 
> In the relative spacial/temporal region of
> Wed, Jan 20, 2010 at 01:21:40PM -0500, Richard Kreiss achieved the
> spontaneous
> generation of the following:
> >
> > Although Ken recommended using low level to go directly to your SQL
> > database, one other solution would be to create an intermediate filepro
> > file(s) mapped to the sql file(s). You can then write any processing
needed
> > to update your filepro records from the intermediate file.  Not an
elegant
> > solution but should work with a minimum of programming.
> 
> You would map over varchar(NNN) -how-, exactly?
> 
> mark->

Mark,

I think I would need to know the possible limits of the particular field in
question.  When I set up the routine I am using, the data being passed for
one file is shipping address used by the UPS WorldShip program.  My filepro
program update a smaller file with had the store name and address.  The
Worldship program is linked to this file and uses the information when
printing labels.  This allows for one master file to maintain all of the
ship to information.

The other place is for order headers, once an order is shipped, the UPS
tracking number, number of cartons, weight and shipping date updates this
file.  When the order is accessed on the filepro side, processing checks for
the shipping information, and if present, updates it.  Yes, I could keep
this as dummy fields to display the information but my client wants it as
part of the original order header record.

Now this is a simple use of fpodbc and may not cover all of the problems of
linking fp to an odbc database, so I did not have the problem of having to
contend with a variable character length field.  It is our data not theirs
that set the field limit.

Richard