I see you posted this months ago, but here goes....
I have realized that many import issues to Quickbooks, and other programs I
imagine, all have some kind of odd thing like this. And if you fix it for
one guy, the other guy does it the first way. It never ends.
I think there are two ways to go conceptually, and the details will depend
on the client.
1. Have them adjust Quickbooks to match ShopSite's database fields. It's
not easy because you are asking a client to change how they work internally.
But if an import/export is needed to save time, this is a no cash solution
to escape more programming on top of ShopSite.
2. Using ShopSite's API, parse the data, store it in a database that
duplicates your client's database, then write an interface to allow your
client to get that data. Your client's order information would come from
your database, not ShopSite's.
Jeremy
Jeremy Bloom
Web Site Consultant
MyVirtualWebStaff
NYC, NY
212/253-6865 (voice)
917/864-5654 (cell)
760/281-7902 (fax)
http://www.MyVirtualWebStaff.com
From: Chris <sawdust@mlcswoodworking.com
Organization: MLCS
Newsgroups: forum.shopsite
Date: Thu, 06 Jun 2002 12:51:16 -0400
Subject: Re: A name is a name is a name
We had to have a script written to parse the field, as Loren suggested in
another post. HOWEVER, this is a less than perfect solution, as it doesn't
work so well if people use middle names, 2 word last names, etc.
Does anyone have a better suggestion?
Chris
mlcswoodworking.com
Wes Rolley wrote:
Shopsite only uses an entire name field. My customer's back office
processes use a FirstName, LastName field and put initials into the
FirstName field if required for CC processing.
Is there an easy way to make ShopSite utilize FirstName, LastName? or is
the best solution to parse the CC Name Field 0-PayName when mapping one
set of data to the other? I need to end up with the name that will be
charged with the CC number, as this is done downstream, Just as 1-800
number and catalog (snail mail) sales are processed.