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 ("whatever"), or INSERT INTO table FROM ARRAY
arrayname, or APPEND FROM ARRAY arrayname, or SCATTER/GATHER MEMVAR or
SCATTER/GATHER arrayname. Interesting also that SCATTER MEMVAR
actually created a variable that can't be referenced because it has
the "-" in it.
Fred
On Tue, Nov 2, 2010 at 10:57 AM, Kurt Wendt <[email protected]> wrote:
> 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 replaced
> with Underscores. Once I had the new structural file built - that's when I
> used it to create the DBF's in the DBC.
>
> Hope that makes more sense - and therefore - how I created my own problem!
>
> In the end - between 3 different type DBF files, I had to build up about 300
> fields - which I DEFINITELY would NOT have wanted to do by hand...
>
> :-)
> -K-
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Fred Taylor
> Sent: Monday, November 01, 2010 6:02 PM
>
> 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 field name was
> not what was chosen.
>
> If you try to create a table from code using CREATE tablename (field-name
> C(10)), you at least get a syntax error.
>
> Fred
>
>
>
> On Mon, Nov 1, 2010 at 2:26 PM, Dan Covill <[email protected]> wrote:
>> 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.
>> Seems to me that the DBC shouldn't allow you to generate or attach a
>> table that has invalid field names. An error when replacing data is
>> way too late!
>>
>> Dan Covill
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
