Re: Sage Export
- From: "Jason Chapman" <jason@xxxxxxxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 12:49:48 +0100
"Stuart Barrett"
Hi
The database used within the Sage Line 50 range of products is
proprietary. Althought I believe the Payroll module uses an MSAccess
database.
To access the customer/supplier addresses we use the ODBC
We found the SDO to be very slow when access more than a few hundred
records across a network so we always use the ODBC Driver to access
data and only use SDO for posting Invoices etc..
Does Sage have batch processing within the GUI for importing CSV / XML / EDI
files?
We are likely to come up against the same kind of issues soon as we intend
extracting via ODBC, marrying with an admin system and possibly building
files to:
- Create Customers
- Create Invoices
Also, as a developer who has bought into the SDO would you be able to write
a set of consumable classes in a Delphiesk way to allow us to do the
injection of records?
If so, how much effort and how much cash :-)
Does the license prohibit it and does it require any runtime element that
needs installing on the client?
Cheers,
JAC.
.
- Follow-Ups:
- Re: Sage Export
- From: Stuart Barrett
- Re: Sage Export
- References:
- Sage Export
- From: no-one
- Re: Sage Export
- From: Stuart Barrett
- Sage Export
- Prev by Date: Re: FastMM and memory leaks
- Next by Date: Re: FastMM and memory leaks
- Previous by thread: Re: Sage Export
- Next by thread: Re: Sage Export
- Index(es):
Relevant Pages
|