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.

So - at this point, I just fix the structural DBF file -  re-create those files 
in the DBC again - and I guess 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 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 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 didn't 
> realize I should ALSO swap out the Dashes.
>
> Once I had that structural file - I simply issued the command:
> CREATE Po_Header Database eCommHub FROM 
> "M:\P-Drive\CUSTOMER\Comint\eComm\PO_H_Struct.DBF"
>
> That PO_H_Struct file is the structural extended type file.
>
> I guess my best option is to remove that DBF from the DBC, fix up the 
> Structural file - then re-create the Po_Header DBF again...
>
> Thanks for your feedback Fred!
>
> -K-
>
>
> -----Original Message-----
> From: profoxtech-boun...@leafe.com 
> [mailto:profoxtech-boun...@leafe.com] On Behalf Of Fred Taylor
> Sent: Monday, November 01, 2010 2:43 PM
>
> 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 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 long names.
>>
>> Hate to admit - I haven't done a lot of work with DBC's (as they do 
>> NOT do it here a my current job) - and I did work with them at my 
>> previous VFP job circa '05-'07. But, I don't remember getting this kind of 
>> error.
>>
>>
>> I created the DBC, and several DBF files within it. But, I have a 
>> bunch of fields that have a Dash instead of an Underscore. When my 
>> program tried to save the data to one of those fields - I got an 
>> error. I figured that it just did NOT like the Dash in the field name.
>> So - I attempted to just change the structure - and change the Dash 
>> into an Underscore - and that's when I got the Error.
>>
>> Is the Dash really not allowed in a field name (even the long field 
>> names within a DBF in a DBC)?
>>
>> At this point I am kinda stuck - and can't really proceed with this 
>> project until I can get the sucker fixed!
>>
>> Thanks in advance...
>>
>>
>>  -K-
>
[excessive quoting removed by server]

_______________________________________________
Post Messages to: ProFox@leafe.com
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/289ea162f5642645b5cf64d624c66a1409df1...@us-ny-mail-002.waitex.net
** 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.

Reply via email to