There is actually another possible approach to the 2 GB limit problem, and
that is to divide your database into two RBASE databases, and use
SCONNECT / SATTACH when connected to database A to reference
tables in database B. I have not made extensive use of this technique, but I
believe there are members of this list who have, so you might hear from them --
We'll all do our best to keep you in the good graces of the NZ Police.
. . . Bob S.
At 03:48 PM 9/15/03, you wrote:
Bob,
Not so good is it? I am going to Chicago (via LA) next Thursday for a three day meeting, maybe I should apply for refugee status in the USA in order to stay away from the NZ Police.
Looks like I'm a bit stuck now. I have done so much programming work in Rbase, I mean there are countless modules that do very clever things, and I would hate to loose all that and have to start converting this to some obscure language like VB or RB.
How about using some other database engine let's say mySQL or ORACLE and then use Rbase to talk to it through ODBC could that be a viable option for me to pursue? Anybody out there who has done this?
Thanks
Frank
------------------------------------------------------------ Bob Simms Robert A. Simms and Co., Los Angeles 818-345-5306 Fax 818-345-5136 E-Mail: mailto:[EMAIL PROTECTED] URL: http://www.pacificnet.net/simms -------------------------------------------------------------

