Dan,
have you tried this?
It does work.
Selecting into a cursor works (no problems with long names)-> Problem is
that it is readonly.
useing it again with a different alias as I posted makes the new alias R/W.
The long names are retained...
Try it on a test table.
select * from longfieldnames_table_in_a_dbc into cursor temp
use dbf("temp") again in 0 alias writable_cursor
rr
-----Original Message-----
From: Dan Covill [mailto:dcovill .at. san DO.T rr.com]
Sent: Thursday, Jun 12, 03 11:44 AM
To: profoxtech@leafe.com
Subject: RE: Long field names
Randy:
Still not sure how you got there, but if the long names are in the DBC and
you need to extract, cursors always allow long names. If you try to make a
free table from any of it, you'll have the same problem again.
As you've figured out <g>, this is why many of us never use the "long field
name" feature. If it was me (thank God it's not!), and I was going to
maintain this app, I would go back and do whatever it took to get rid of
those long field names.
Dan Covill
At 16:21 06/11/03 -0700, Randy Roberts wrote:
>Hi Dan
>I believe I have come up with a simple solution and I'll bounce it out here
>for y'all to critique...
>
>select * from longfieldnames_table_in_a_dbc into cursor temp
>use dbf("temp") again in 0 alias writable_cursor
>
>simple and it works!
>
>What do you think?
[excessive quoting removed by server]
©2003 Randy Roberts |
