Nope. But, didn't have to - since I resolved the problem by fixing the actual
DBF structure.
-K-
-Original Message-
From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On
Behalf Of Gianni Turri
Sent: Monday, November 01, 2010 6:22 PM
Have you tried to put the
Dan - I totally agree with you! Especially, since, when you get to the
point of trying to do a Replace, and if you didn't know that the Dash
was not allowed (I just wasn't sure at first, since I figured things
might be handled differently for the longer DBF field names in a DBC) -
its frustrating
Fred,
Actually - what I did was create that Structural type DBF based upon a Good
DBF. Then, I wiped out the actual data in the DBF and filled it myself, and
then I did a whole bunch of manipulations, like replacing certain longer words
(Company w/Co, Authorization w/Auth, etc) and spaces
The problem wasn't so much that you created your own problem, it was
that VFP allowed you to create it in an unusable fashion. I was
surprised that it allowed it without even so much as a warning.
The only way I found to get data into the fields with dashes was
INSERT INTO table VALUES
I have this new project I am working on - and for this project I decided
to go with a DBC - since the Data files I need to import (from an
outside source) have long field name descriptions in thier
documentation. Figured it would make it easier to keep track of the
fields thier meaning if I did
Correct, dashes are not allowed in a field name. How did you manage
to define your tables with dashes in there?
Fred
On Mon, Nov 1, 2010 at 11:29 AM, Kurt Wendt kurtwe...@waitex.com wrote:
I have this new project I am working on - and for this project I decided
to go with a DBC - since the
I created one of those type of Structure Extended files. But, I built that file
up myself - grabbing up field names from this documentation I had from this
eCommerce company. And, in prepping the field names, where ever there was a
blank between words - I replaced it with an Underscore. But, I
I tried to create a table the way you did, and all I got was the part
of the field name before the -. IE, your field name was A-B-C and
my result was a table with field name A only. Strange there was no
error generated, either.
Fred
On Mon, Nov 1, 2010 at 11:51 AM, Kurt Wendt
Check that, I did get a table with the field with the dashes, but
unable to REPLACE any value in it. It was a cursor that created the
A field only (from an array).
Fred
On Mon, Nov 1, 2010 at 11:51 AM, Kurt Wendt kurtwe...@waitex.com wrote:
I created one of those type of Structure Extended
that shall do it...
-K-
-Original Message-
From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On
Behalf Of Fred Taylor
Sent: Monday, November 01, 2010 3:21 PM
To: profoxt...@leafe.com
Subject: Re: A DBC an Err: Object Name is Invalid
Check that, I did get a table
On 11/1/2010 12:54 PM, Kurt Wendt wrote:
Yeah - exactly. I got an error when trying to replace data into the field -
and that's when I tried to change the data structure - and got the next error
as noted in the Subject.
Looks like there are a couple of problems with VFP's handling of this.
I was surprised that there was no error when creating a table from the
data in COPY STRUCTURE EXTENDED, or the cursor created with the array
from AFIELDS and the field name column tweaked with dashes. At least
the cursor created a name that was usable, but still no error or any
indication the
Have you tried to put the offending fieldname between double quote?
field-name
Gianni
On Mon, 1 Nov 2010 15:01:56 -0700, Fred Taylor fbtay...@gmail.com wrote:
I was surprised that there was no error when creating a table from the
data in COPY STRUCTURE EXTENDED, or the cursor created with the
Doesn't work.
Fred
On Mon, Nov 1, 2010 at 3:22 PM, Gianni Turri gianni...@gmail.com wrote:
Have you tried to put the offending fieldname between double quote?
field-name
Gianni
On Mon, 1 Nov 2010 15:01:56 -0700, Fred Taylor fbtay...@gmail.com wrote:
I was surprised that there was no
14 matches
Mail list logo
