------=_NextPart_000_0049_01C3D86B.94ABC050
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Someone told me about this group, hopefully I can get some help ...
here's a post I put on the Miva user's group.
=20
[email protected] <mailto:[email protected]>=20
=20
Does anyone have any similar experiences with Miva Synchro - I really
need this product bad, but I can't get the initial loads to work even
with just a couple of test orders. If there is anyone that knows
Quickbooks/Synchro, I'm happy to pay a reasonable fee for some help to
get this to work. I am in contact with Miva technical support, which
will be several days for each problem, and looking for a little quicker
way to get synchro working.
=20
We're not having much luck getting Synchro to work - I would suspect
when it works, it works well, but I think that the Miva team didn't
figure that existing Quickbooks files would need some adjustments to
insure that it works - and there is no service to evaluate any
compatibility issues between your quickbooks approach and the Miva (for
example, our product info is loaded consistently to quickbooks and =
Miva,
Customers in Miva are different - user assigned customer names =
usually).
There is absputely no forgiveness if there are any errors, and if there
are errors, the synchronizations abort with a cryptic error that has no
meaning - here are two of the errors that I get now:
=20
Quickbooks Error: Object "39B0000-1072807098" specified in the request
cannot be found. Quickbooks error message: Invalid argument. The
specified record does not exist in the list.
=20
Quickbooks Error: The query request has not been fully completed. There
was a required elements (1D70000-1072933686') that could not be found =
in
quickbooks.
=20
Absolutely no clue what's happening, and then the synchronization
aborts.=20
When I start with a blank quickbook file, things work better, and my
hopes come up ... until I try on a copy of my active Quickbooks file,
and then the uploads abort on the first record!
------=_NextPart_000_0049_01C3D86B.94ABC050--
Comment