AREV -] Access and back (and licensing) (AREV Specific)
At 02 MAY 2005 03:25:18PM Charles Milner wrote:
I've got a client using the application my company developed using AREV 2.03.
They have a number of different office locations, and keep a separate runtime version at each location, with separate data.
Exchanging data between offices is not too difficult - the data stays in AREV format - we just have aprogram which FILECOPYs what it needs to a folder, then the data is e-mailed to the other locations.
Recently the client acquired another company and they're trying to integrate the 2 different office systems.
They still want to use our application.
But the new offices use an application written in Access.
So the problem is, how to send the data to the other location so it can be read into Access.
Data has to be exchanged between all the various offices, as well as a acntral location, so I don't really want to require them to choose a "export to Access" option, or an "export to Arev" option. They just to send the data regardless of the system at the destination. Or read the data regardless of the source.
One idea is to take a "stripped-down" AREV runtime, installed at the new office, which runs just enough to attach to the AREV data files, then have a VB program call the AREV runtime with a command line telling it what data it wants, etc.
My question is: is there an alternative to this method - ie. a way to write a VB app which can read AREV 2.03 lh files?
And: is this permitted within the AREV licensing rules? The client does have the runtime version (we use the development version). And they have the appropriate BUMP disks to match the various users at each office location.
At 02 MAY 2005 11:59PM Warren Auyong wrote:
You might be able to use DBase III files. Access -] ODBC -] DB3 ← DB3 bond ← ARev. You could use the Revelation ODBC drivers, but that is read-only. The DBase bond really is for demo purposes only. I've not tested it's full capabilities and I don't know what glitches exist in it.
There are some DOS utilities that allow you to read LH files. Writing to them would be a major undertaking to develop a compatible LH engine.
At 03 MAY 2005 01:30AM Curt Putnam wrote:
I guess I've used the dBeast bond more than Warren and would suggest that, as long as you aren't dealing with multiple simultaneous users of the bonded files, they will work fine for your purposes. Using the bond, Arev will treat the bonded file pretty transparently. Access will happily import/export dBeast.