Migration from XBase++ to Visual FoxPro 9

Hi,

I am working on a project in Visual FoxPro 9 which will eventually replace
the existing software written in XBase++.
During this migration process, I will use the existing XBase++ tables with
cdx indexes.

Does anyone have any recommendations or any data recommendations during this
migration.

I seem to have random index problems. The problem will not be there and then
it shows up. I then delete the index file and reindex with the XBase++
software and the VFP9 software will still show the error. I then open the
free table and the index in VFP9 and then issue reindex (This is done
without trying to browse the table). All is cured. The table is still
accessable from XBase++ software and VFP9 software. Anybody know what is
going on here and what I need to start doing in order to make this work?

Thank you,

Mike

man-wai
Wed Aug 17 09:13:59 CDT 2005

> I seem to have random index problems. The problem will not be there and then
> it shows up. I then delete the index file and reindex with the XBase++

Did you really mean "REINDEX"? Don't reindex. Delete all old index and
tags. Rebuild it from scratch using the same expression. Use CDX index tag.

--
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70

Michael
Wed Aug 17 10:13:13 CDT 2005

Mike,

I deleted the index file and then rebuilt the index in XBase++. The error
was still there.

In VFP9, all I did was issue the reindex command and the problem went away.
Now the table with cdx index works in both.

When the error came up in VFP9, I could still go in the old software and no
error.

Maybe I should only index in VFP9. I am a little confused why VFP is giving
me an error with free dbf table with cdx index. Is there some compatability
setting I should turn on?

I am looking for suggestions.

Thank you,

Mike


"man-wai chang" <toylet.toylet@gmail.com> wrote in message
news:O6xiqXzoFHA.1872@TK2MSFTNGP10.phx.gbl...
>> I seem to have random index problems. The problem will not be there and
>> then it shows up. I then delete the index file and reindex with the
>> XBase++
>
> Did you really mean "REINDEX"? Don't reindex. Delete all old index and
> tags. Rebuild it from scratch using the same expression. Use CDX index
> tag.
>
> --
> .~. Might, Courage, Vision. http://www.linux-sxs.org
> / v \
> /( _ )\ Linux 2.4.31
> ^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70

Dan
Wed Aug 17 11:01:37 CDT 2005

What error message are you getting?

It sounds like xbase++ may not be fully compatible.

Be VERY wary of sharing data between disparate dbms programs. You might want
to access the dbf's from the Fox side using ODBC.

Dan


Michael Wheat wrote:
> Hi,
>
> I am working on a project in Visual FoxPro 9 which will eventually
> replace the existing software written in XBase++.
> During this migration process, I will use the existing XBase++ tables
> with cdx indexes.
>
> Does anyone have any recommendations or any data recommendations
> during this migration.
>
> I seem to have random index problems. The problem will not be there
> and then it shows up. I then delete the index file and reindex with
> the XBase++ software and the VFP9 software will still show the error.
> I then open the free table and the index in VFP9 and then issue
> reindex (This is done without trying to browse the table). All is
> cured. The table is still accessable from XBase++ software and VFP9
> software. Anybody know what is going on here and what I need to
> start doing in order to make this work?
>
> Thank you,
>
> Mike

Paul
Wed Aug 17 13:22:52 CDT 2005

I use REINDEX all the time. Never have any trouble with it.


"man-wai chang" <toylet.toylet@gmail.com> wrote in message
news:O6xiqXzoFHA.1872@TK2MSFTNGP10.phx.gbl...
>> I seem to have random index problems. The problem will not be there and
>> then it shows up. I then delete the index file and reindex with the
>> XBase++
>
> Did you really mean "REINDEX"? Don't reindex. Delete all old index and
> tags. Rebuild it from scratch using the same expression. Use CDX index
> tag.
>
> --
> .~. Might, Courage, Vision. http://www.linux-sxs.org
> / v \
> /( _ )\ Linux 2.4.31
> ^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70

Paul
Wed Aug 17 13:25:11 CDT 2005

What do you mean, "random index problems"? What exactly is happening? Do you
get error messages? When?

Be aware that if you use certain VFP9 features, integer fields for instance,
old software might get confused. Also, are you sure that xbase can use cdx
files? Perhaps it's restricted to idx/ndx.



"Michael Wheat" <mikewheat@tm.net> wrote in message
news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I am working on a project in Visual FoxPro 9 which will eventually replace
> the existing software written in XBase++.
> During this migration process, I will use the existing XBase++ tables with
> cdx indexes.
>
> Does anyone have any recommendations or any data recommendations during
> this migration.
>
> I seem to have random index problems. The problem will not be there and
> then it shows up. I then delete the index file and reindex with the
> XBase++ software and the VFP9 software will still show the error. I then
> open the free table and the index in VFP9 and then issue reindex (This is
> done without trying to browse the table). All is cured. The table is
> still accessable from XBase++ software and VFP9 software. Anybody know
> what is going on here and what I need to start doing in order to make this
> work?
>
> Thank you,
>
> Mike
>

Ook
Wed Aug 17 13:44:40 CDT 2005

Sooner or later it will bite you. I've seen several index problems that
REINDEX did not fix, but deleting and recreating the CDX did fix.

"Paul Pedersen" <no-reply@swen.com> wrote in message
news:e9Azxi1oFHA.3304@tk2msftngp13.phx.gbl...
>I use REINDEX all the time. Never have any trouble with it.
>
>
> "man-wai chang" <toylet.toylet@gmail.com> wrote in message
> news:O6xiqXzoFHA.1872@TK2MSFTNGP10.phx.gbl...
>>> I seem to have random index problems. The problem will not be there and
>>> then it shows up. I then delete the index file and reindex with the
>>> XBase++
>>
>> Did you really mean "REINDEX"? Don't reindex. Delete all old index and
>> tags. Rebuild it from scratch using the same expression. Use CDX index
>> tag.
>>
>> --
>> .~. Might, Courage, Vision. http://www.linux-sxs.org
>> / v \
>> /( _ )\ Linux 2.4.31
>> ^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70
>
>

Paul
Wed Aug 17 14:35:36 CDT 2005

I had one once, many years ago. Old version, obviously - it might even have
been FPW2.6, I don't remember now.

We've had this discussion before. Maybe you're doing it wrong. ;-)



"Ook" <no usenet spam at zoot al dot com> wrote in message
news:uFqEr71oFHA.3996@TK2MSFTNGP12.phx.gbl...
> Sooner or later it will bite you. I've seen several index problems that
> REINDEX did not fix, but deleting and recreating the CDX did fix.
>
> "Paul Pedersen" <no-reply@swen.com> wrote in message
> news:e9Azxi1oFHA.3304@tk2msftngp13.phx.gbl...
>>I use REINDEX all the time. Never have any trouble with it.
>>
>>
>> "man-wai chang" <toylet.toylet@gmail.com> wrote in message
>> news:O6xiqXzoFHA.1872@TK2MSFTNGP10.phx.gbl...
>>>> I seem to have random index problems. The problem will not be there and
>>>> then it shows up. I then delete the index file and reindex with the
>>>> XBase++
>>>
>>> Did you really mean "REINDEX"? Don't reindex. Delete all old index and
>>> tags. Rebuild it from scratch using the same expression. Use CDX index
>>> tag.
>>>
>>> --
>>> .~. Might, Courage, Vision. http://www.linux-sxs.org
>>> / v \
>>> /( _ )\ Linux 2.4.31
>>> ^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70
>>
>>
>
>

Michael
Wed Aug 17 15:42:09 CDT 2005

Paul,

The tables were created using XBase++, not VFP. There are no integer fields
in the tables.
XBase++ is compatible with cdx indexes. I've been using them with XBase++
for about 5 years now.

Most of the time, there is no problem with using the XBase++ tables with
VFP9, but when the problem does show up, it does not go away until I issue a
reindex from VFP9. The problem only occurs when opening the table with VFP9
software. I can still get into the table with XBase++ table.

Thank you,

Mike

"Paul Pedersen" <no-reply@swen.com> wrote in message
news:u7FqEk1oFHA.3156@TK2MSFTNGP10.phx.gbl...
> What do you mean, "random index problems"? What exactly is happening? Do
> you get error messages? When?
>
> Be aware that if you use certain VFP9 features, integer fields for
> instance, old software might get confused. Also, are you sure that xbase
> can use cdx files? Perhaps it's restricted to idx/ndx.
>
>
>
> "Michael Wheat" <mikewheat@tm.net> wrote in message
> news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
>> Hi,
>>
>> I am working on a project in Visual FoxPro 9 which will eventually
>> replace the existing software written in XBase++.
>> During this migration process, I will use the existing XBase++ tables
>> with cdx indexes.
>>
>> Does anyone have any recommendations or any data recommendations during
>> this migration.
>>
>> I seem to have random index problems. The problem will not be there and
>> then it shows up. I then delete the index file and reindex with the
>> XBase++ software and the VFP9 software will still show the error. I then
>> open the free table and the index in VFP9 and then issue reindex (This is
>> done without trying to browse the table). All is cured. The table is
>> still accessable from XBase++ software and VFP9 software. Anybody know
>> what is going on here and what I need to start doing in order to make
>> this work?
>>
>> Thank you,
>>
>> Mike
>>
>
>

Ook
Wed Aug 17 15:19:30 CDT 2005

That is always possible LOL. Truthfully, I've not been bit by this in years,
it's quite possible that it's no longer an issue. I used the Visual
ProMatrix framework for several years, and let their own reindex routine
handle this which, IIRC, actually dissasociates the DBF from the DBC,
creates a dummy DBC, drops the CDX, recreates it, and reassociates the DBF
with the correct DBC. Way too much work for a reindex, and in a few cases
fails to fix DBC problems that would otherwise have been fixed. Now I'm on
my own again and I'll probably continue to do it my way simply it works and
I have no compelling reason to change :)

"Paul Pedersen" <no-reply@swen.com> wrote in message
news:evTZaL2oFHA.3316@tk2msftngp13.phx.gbl...
>I had one once, many years ago. Old version, obviously - it might even have
>been FPW2.6, I don't remember now.
>
> We've had this discussion before. Maybe you're doing it wrong. ;-)
>
>
>
> "Ook" <no usenet spam at zoot al dot com> wrote in message
> news:uFqEr71oFHA.3996@TK2MSFTNGP12.phx.gbl...
>> Sooner or later it will bite you. I've seen several index problems that
>> REINDEX did not fix, but deleting and recreating the CDX did fix.
>>
>> "Paul Pedersen" <no-reply@swen.com> wrote in message
>> news:e9Azxi1oFHA.3304@tk2msftngp13.phx.gbl...
>>>I use REINDEX all the time. Never have any trouble with it.
>>>
>>>

man-wai
Wed Aug 17 21:01:32 CDT 2005

> Most of the time, there is no problem with using the XBase++ tables with
> VFP9, but when the problem does show up, it does not go away until I issue a
> reindex from VFP9. The problem only occurs when opening the table with VFP9
> software. I can still get into the table with XBase++ table.

What if you make both sides use the old dBase index file format?

Eugene
Wed Aug 17 21:59:09 CDT 2005

Dan Freeman wrote:
> What error message are you getting?
>
> It sounds like xbase++ may not be fully compatible.
>
> Be VERY wary of sharing data between disparate dbms programs. You might want
> to access the dbf's from the Fox side using ODBC.
>

I also recommend using ODBC to access the data. You will be that much
closer to a true client server architecture if you need to go that way
someday.


> Dan
>
>
> Michael Wheat wrote:
>
>>Hi,
>>
>>I am working on a project in Visual FoxPro 9 which will eventually
>>replace the existing software written in XBase++.
>>During this migration process, I will use the existing XBase++ tables
>>with cdx indexes.
>>
>>Does anyone have any recommendations or any data recommendations
>>during this migration.
>>
>>I seem to have random index problems. The problem will not be there
>>and then it shows up. I then delete the index file and reindex with
>>the XBase++ software and the VFP9 software will still show the error.
>>I then open the free table and the index in VFP9 and then issue
>>reindex (This is done without trying to browse the table). All is
>>cured. The table is still accessable from XBase++ software and VFP9
>>software. Anybody know what is going on here and what I need to
>>start doing in order to make this work?
>>
>>Thank you,
>>
>>Mike
>
>
>

Anders
Thu Aug 18 06:47:59 CDT 2005

What is the error message? What is th inde expression?
-Anders


Den 05-08-17 17.13, i artikeln ekni04zoFHA.764@TK2MSFTNGP14.phx.gbl, skrev
"Michael Wheat" <mikewheat@tm.net>:

> Mike,
>
> I deleted the index file and then rebuilt the index in XBase++. The error
> was still there.
>
> In VFP9, all I did was issue the reindex command and the problem went away.
> Now the table with cdx index works in both.
>
> When the error came up in VFP9, I could still go in the old software and no
> error.
>
> Maybe I should only index in VFP9. I am a little confused why VFP is giving
> me an error with free dbf table with cdx index. Is there some compatability
> setting I should turn on?
>
> I am looking for suggestions.
>
> Thank you,
>
> Mike
>
>
> "man-wai chang" <toylet.toylet@gmail.com> wrote in message
> news:O6xiqXzoFHA.1872@TK2MSFTNGP10.phx.gbl...
>>> I seem to have random index problems. The problem will not be there and
>>> then it shows up. I then delete the index file and reindex with the
>>> XBase++
>>
>> Did you really mean "REINDEX"? Don't reindex. Delete all old index and
>> tags. Rebuild it from scratch using the same expression. Use CDX index
>> tag.
>>
>> --
>> .~. Might, Courage, Vision. http://www.linux-sxs.org
>> / v \
>> /( _ )\ Linux 2.4.31
>> ^ ^ 10:12pm up 2 days 41 min load average: 1.74 1.71 1.70
>
>

Michael
Thu Aug 18 07:42:51 CDT 2005

That is what causes the problem.

The problem goes away when I issue reindex in VFP9.

Mike

"man-wai chang" <toylet.toylet@gmail.com> wrote in message
news:eoNjBj5oFHA.2080@TK2MSFTNGP14.phx.gbl...
>> Most of the time, there is no problem with using the XBase++ tables with
>> VFP9, but when the problem does show up, it does not go away until I
>> issue a
>> reindex from VFP9. The problem only occurs when opening the table with
>> VFP9
>> software. I can still get into the table with XBase++ table.
>
> What if you make both sides use the old dBase index file format?

swdev2
Thu Aug 18 08:42:27 CDT 2005

Heya Michael .
We do both xBase++ and VFP in my shop - so if you need some guidance -
contact me at one of the addy's listed in the websites below.

Ain't it goofy? If you'll check the hex values of the cdx in the first 10
bytes, in an index untouched by vfp9,
and then compare one written by VFP9, you'll notice that they are different.

The indexing scheme for CDX's from xBase++ is ONLY FoxPro 2.6 compliant, as
I understand it. I could be dead wrong, of course, but that's unlikely.
There is a gnat's whisker's bit o difference in the cdx layout, as I'm sure
you'll find in when you study a CDX file written by xb++ vs VFP.

I'm glad you found 'the trick' - just index IN VFP9 and xbase++ can still
read it. WooFrickenHoo...
mondo regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.dotnetconversions.com
"Michael Wheat" <mikewheat@tm.net> wrote in message
news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I am working on a project in Visual FoxPro 9 which will eventually replace
> the existing software written in XBase++.
> During this migration process, I will use the existing XBase++ tables with
> cdx indexes.
>
> Does anyone have any recommendations or any data recommendations during
this
> migration.
>
> I seem to have random index problems. The problem will not be there and
then
> it shows up. I then delete the index file and reindex with the XBase++
> software and the VFP9 software will still show the error. I then open the
> free table and the index in VFP9 and then issue reindex (This is done
> without trying to browse the table). All is cured. The table is still
> accessable from XBase++ software and VFP9 software. Anybody know what is
> going on here and what I need to start doing in order to make this work?
>
> Thank you,
>
> Mike
>
>

Michael
Thu Aug 18 11:12:24 CDT 2005

Bill,

Thank you for responding to this post. I thought maybe I was the only
person who used XBase++ and VFP.

Thank you for confirming what I thought was the correct way to resolve the
problem.

Mike

"swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
news:u2SEQs$oFHA.1416@TK2MSFTNGP09.phx.gbl...
> Heya Michael .
> We do both xBase++ and VFP in my shop - so if you need some guidance -
> contact me at one of the addy's listed in the websites below.
>
> Ain't it goofy? If you'll check the hex values of the cdx in the first 10
> bytes, in an index untouched by vfp9,
> and then compare one written by VFP9, you'll notice that they are
> different.
>
> The indexing scheme for CDX's from xBase++ is ONLY FoxPro 2.6 compliant,
> as
> I understand it. I could be dead wrong, of course, but that's unlikely.
> There is a gnat's whisker's bit o difference in the cdx layout, as I'm
> sure
> you'll find in when you study a CDX file written by xb++ vs VFP.
>
> I'm glad you found 'the trick' - just index IN VFP9 and xbase++ can still
> read it. WooFrickenHoo...
> mondo regards [Bill]
> --
> ===================
> William Sanders / EFG VFP / mySql / MS-SQL
> www.efgroup.net/vfpwebhosting
> www.dotnetconversions.com
> "Michael Wheat" <mikewheat@tm.net> wrote in message
> news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
>> Hi,
>>
>> I am working on a project in Visual FoxPro 9 which will eventually
>> replace
>> the existing software written in XBase++.
>> During this migration process, I will use the existing XBase++ tables
>> with
>> cdx indexes.
>>
>> Does anyone have any recommendations or any data recommendations during
> this
>> migration.
>>
>> I seem to have random index problems. The problem will not be there and
> then
>> it shows up. I then delete the index file and reindex with the XBase++
>> software and the VFP9 software will still show the error. I then open
>> the
>> free table and the index in VFP9 and then issue reindex (This is done
>> without trying to browse the table). All is cured. The table is still
>> accessable from XBase++ software and VFP9 software. Anybody know what is
>> going on here and what I need to start doing in order to make this work?
>>
>> Thank you,
>>
>> Mike
>>
>>
>
>

swdev2
Thu Aug 18 13:07:43 CDT 2005

Greetings Michael -
you are QUITE WELCOME.
mondo regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.dotnetconversions.com
"Michael Wheat" <mikewheat@tm.net> wrote in message
news:OeFww#ApFHA.1464@TK2MSFTNGP14.phx.gbl...
> Bill,
>
> Thank you for responding to this post. I thought maybe I was the only
> person who used XBase++ and VFP.
>
> Thank you for confirming what I thought was the correct way to resolve the
> problem.
>
> Mike
[snip]

Jan
Sat Aug 20 02:34:58 CDT 2005

Mike,

From what I have read in all the posts, it seems to me that your problem is
a compatibility issue between XBase++ and VFP9 which is causing the table
checking on open to flag a problem. Check out the set tablevalidate command.

HTH
Jan

"Michael Wheat" <mikewheat@tm.net> wrote in message
news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I am working on a project in Visual FoxPro 9 which will eventually replace
> the existing software written in XBase++.
> During this migration process, I will use the existing XBase++ tables with
> cdx indexes.
>
> Does anyone have any recommendations or any data recommendations during
> this migration.
>
> I seem to have random index problems. The problem will not be there and
> then it shows up. I then delete the index file and reindex with the
> XBase++ software and the VFP9 software will still show the error. I then
> open the free table and the index in VFP9 and then issue reindex (This is
> done without trying to browse the table). All is cured. The table is
> still accessable from XBase++ software and VFP9 software. Anybody know
> what is going on here and what I need to start doing in order to make this
> work?
>
> Thank you,
>
> Mike
>

Michael
Thu Aug 25 11:51:21 CDT 2005

Jan,

I found a post about the SET TABLEVALIDATE TO command earlier, but someone
said when they switched to VFP9, that solved all their problems.
I will try it and see if it works.

Thank you,

Mike

"Jan" <nomail@nowhere.com> wrote in message
news:esrBtlVpFHA.3408@tk2msftngp13.phx.gbl...
> Mike,
>
> From what I have read in all the posts, it seems to me that your problem
> is a compatibility issue between XBase++ and VFP9 which is causing the
> table checking on open to flag a problem. Check out the set tablevalidate
> command.
>
> HTH
> Jan
>
> "Michael Wheat" <mikewheat@tm.net> wrote in message
> news:uBsKl3yoFHA.1444@TK2MSFTNGP10.phx.gbl...
>> Hi,
>>
>> I am working on a project in Visual FoxPro 9 which will eventually
>> replace the existing software written in XBase++.
>> During this migration process, I will use the existing XBase++ tables
>> with cdx indexes.
>>
>> Does anyone have any recommendations or any data recommendations during
>> this migration.
>>
>> I seem to have random index problems. The problem will not be there and
>> then it shows up. I then delete the index file and reindex with the
>> XBase++ software and the VFP9 software will still show the error. I then
>> open the free table and the index in VFP9 and then issue reindex (This is
>> done without trying to browse the table). All is cured. The table is
>> still accessable from XBase++ software and VFP9 software. Anybody know
>> what is going on here and what I need to start doing in order to make
>> this work?
>>
>> Thank you,
>>
>> Mike
>>
>
>