Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #12026 > unrolled thread

Mem2String

Started byJames Martin <james@northwoodlumber.com>
First post2018-10-04 17:20 -0400
Last post2018-11-06 10:56 -0500
Articles 20 on this page of 21 — 6 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Mem2String James Martin <james@northwoodlumber.com> - 2018-10-04 17:20 -0400
    Re: Mem2String Mathias <mathias.hakansson@consultec.se> - 2018-10-04 23:43 -0700
      Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-05 08:11 -0400
        Re: Mem2String JohnMartens <martens@tennishulp.info> - 2018-10-05 19:45 +0200
          Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-05 15:48 -0400
            Re: Mem2String JohnMartens <martens@tennishulp.info> - 2018-10-05 22:37 +0200
              Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-05 16:56 -0400
      Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-05 08:39 -0400
    Re: Mem2String "Jamal" <noooospam@example.com> - 2018-10-05 15:41 -0400
      Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-05 17:04 -0400
        Re: Mem2String "Jamal" <noooospam@example.com> - 2018-10-05 17:52 -0400
          Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-06 08:10 -0400
            Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-06 09:36 -0400
              Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-06 12:39 -0400
                Re: Mem2String Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2018-10-09 17:18 +0200
                  Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-10-11 15:21 -0400
                    Re: Mem2String D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-11-05 18:47 +0100
                      Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-11-05 13:00 -0500
                        Re: Mem2String D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-11-05 20:24 +0100
    Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-11-06 10:50 -0500
    Re: Mem2String James Martin <james@northwoodlumber.com> - 2018-11-06 10:56 -0500

Page 1 of 2  [1] 2  Next page →


#12026 — Mem2String

FromJames Martin <james@northwoodlumber.com>
Date2018-10-04 17:20 -0400
SubjectMem2String
Message-ID<pp6078$m99$1@dont-email.me>
I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData 
uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first 
character of a memo field is ASCII 198 and this causes the routine to 
choke - at least I think so. The data is actually a reference to a memo 
field and is 4 characters long. I don't need the memo field information, 
but I do need all the other fields.

What happens is that SQLSelect:GetData reads up to the memo field and 
then none of the rest of the record is read. The next record is read up 
to the memo field again, and so on.

I have tried to change the fieldspec for the field to Character(4) but 
that does not work. I am fwriting information to a file and the 
nODBCType is -1.

Any ideas of what I could do?

James

[toc] | [next] | [standalone]


#12027

FromMathias <mathias.hakansson@consultec.se>
Date2018-10-04 23:43 -0700
Message-ID<0535ea6d-b916-49ca-a424-c004ec55059d@googlegroups.com>
In reply to#12026
Is it a one time conversion? Try Excel.

/Mathias

Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData 
> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first 
> character of a memo field is ASCII 198 and this causes the routine to 
> choke - at least I think so. The data is actually a reference to a memo 
> field and is 4 characters long. I don't need the memo field information, 
> but I do need all the other fields.
> 
> What happens is that SQLSelect:GetData reads up to the memo field and 
> then none of the rest of the record is read. The next record is read up 
> to the memo field again, and so on.
> 
> I have tried to change the fieldspec for the field to Character(4) but 
> that does not work. I am fwriting information to a file and the 
> nODBCType is -1.
> 
> Any ideas of what I could do?
> 
> James

[toc] | [prev] | [next] | [standalone]


#12028

FromJames Martin <james@northwoodlumber.com>
Date2018-10-05 08:11 -0400
Message-ID<pp7ked$r64$1@dont-email.me>
In reply to#12027
No. I would like to generate reports regularly. Anyhow, if I can't open 
it I can't convert it to Excel.

I have a hunch that the routine that reads in the whole record chokes at 
the ascii 198. The data comes in properly until the memo field; the 
fields after that are blank.

James

On 10/05/2018 02:43 AM, Mathias wrote:
> Is it a one time conversion? Try Excel.
> 
> /Mathias
> 
> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>> character of a memo field is ASCII 198 and this causes the routine to
>> choke - at least I think so. The data is actually a reference to a memo
>> field and is 4 characters long. I don't need the memo field information,
>> but I do need all the other fields.
>>
>> What happens is that SQLSelect:GetData reads up to the memo field and
>> then none of the rest of the record is read. The next record is read up
>> to the memo field again, and so on.
>>
>> I have tried to change the fieldspec for the field to Character(4) but
>> that does not work. I am fwriting information to a file and the
>> nODBCType is -1.
>>
>> Any ideas of what I could do?
>>
>> James
> 

[toc] | [prev] | [next] | [standalone]


#12030

FromJohnMartens <martens@tennishulp.info>
Date2018-10-05 19:45 +0200
Message-ID<pp87uu$v4d$1@dont-email.me>
In reply to#12028
I think Mathias question is: Can you open the file in Excel ?
If so you can let Excel save the file as a format that you can read in 
your App



Op 5-10-2018 om 14:11 schreef James Martin:
> No. I would like to generate reports regularly. Anyhow, if I can't open 
> it I can't convert it to Excel.
> 
> I have a hunch that the routine that reads in the whole record chokes at 
> the ascii 198. The data comes in properly until the memo field; the 
> fields after that are blank.
> 
> James
> 
> On 10/05/2018 02:43 AM, Mathias wrote:
>> Is it a one time conversion? Try Excel.
>>
>> /Mathias
>>
>> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>> character of a memo field is ASCII 198 and this causes the routine to
>>> choke - at least I think so. The data is actually a reference to a memo
>>> field and is 4 characters long. I don't need the memo field information,
>>> but I do need all the other fields.
>>>
>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>> then none of the rest of the record is read. The next record is read up
>>> to the memo field again, and so on.
>>>
>>> I have tried to change the fieldspec for the field to Character(4) but
>>> that does not work. I am fwriting information to a file and the
>>> nODBCType is -1.
>>>
>>> Any ideas of what I could do?
>>>
>>> James
>>

[toc] | [prev] | [next] | [standalone]


#12032

FromJames Martin <james@northwoodlumber.com>
Date2018-10-05 15:48 -0400
Message-ID<pp8f67$h3v$1@dont-email.me>
In reply to#12030
I don't have Excel but Libre Office opens the smaller files. Has there 
ever been a Visual Fox Pro RDD for VO?

James

On 10/05/2018 01:45 PM, JohnMartens wrote:
> I think Mathias question is: Can you open the file in Excel ?
> If so you can let Excel save the file as a format that you can read in 
> your App
> 
> 
> 
> Op 5-10-2018 om 14:11 schreef James Martin:
>> No. I would like to generate reports regularly. Anyhow, if I can't 
>> open it I can't convert it to Excel.
>>
>> I have a hunch that the routine that reads in the whole record chokes 
>> at the ascii 198. The data comes in properly until the memo field; the 
>> fields after that are blank.
>>
>> James
>>
>> On 10/05/2018 02:43 AM, Mathias wrote:
>>> Is it a one time conversion? Try Excel.
>>>
>>> /Mathias
>>>
>>> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>>>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>> choke - at least I think so. The data is actually a reference to a memo
>>>> field and is 4 characters long. I don't need the memo field 
>>>> information,
>>>> but I do need all the other fields.
>>>>
>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>> then none of the rest of the record is read. The next record is read up
>>>> to the memo field again, and so on.
>>>>
>>>> I have tried to change the fieldspec for the field to Character(4) but
>>>> that does not work. I am fwriting information to a file and the
>>>> nODBCType is -1.
>>>>
>>>> Any ideas of what I could do?
>>>>
>>>> James
>>>

[toc] | [prev] | [next] | [standalone]


#12033

FromJohnMartens <martens@tennishulp.info>
Date2018-10-05 22:37 +0200
Message-ID<pp8i2q$2ju$1@dont-email.me>
In reply to#12032
So calc won't open your file because it is to big ?


Op 5-10-2018 om 21:48 schreef James Martin:
> I don't have Excel but Libre Office opens the smaller files. Has there 
> ever been a Visual Fox Pro RDD for VO?
> 
> James
> 
> On 10/05/2018 01:45 PM, JohnMartens wrote:
>> I think Mathias question is: Can you open the file in Excel ?
>> If so you can let Excel save the file as a format that you can read in 
>> your App
>>
>>
>>
>> Op 5-10-2018 om 14:11 schreef James Martin:
>>> No. I would like to generate reports regularly. Anyhow, if I can't 
>>> open it I can't convert it to Excel.
>>>
>>> I have a hunch that the routine that reads in the whole record chokes 
>>> at the ascii 198. The data comes in properly until the memo field; 
>>> the fields after that are blank.
>>>
>>> James
>>>
>>> On 10/05/2018 02:43 AM, Mathias wrote:
>>>> Is it a one time conversion? Try Excel.
>>>>
>>>> /Mathias
>>>>
>>>> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>>>>> I am reading an unusual DBF via ODBC and the standard 
>>>>> SQLSelect:GetData
>>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>>> choke - at least I think so. The data is actually a reference to a 
>>>>> memo
>>>>> field and is 4 characters long. I don't need the memo field 
>>>>> information,
>>>>> but I do need all the other fields.
>>>>>
>>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>>> then none of the rest of the record is read. The next record is 
>>>>> read up
>>>>> to the memo field again, and so on.
>>>>>
>>>>> I have tried to change the fieldspec for the field to Character(4) but
>>>>> that does not work. I am fwriting information to a file and the
>>>>> nODBCType is -1.
>>>>>
>>>>> Any ideas of what I could do?
>>>>>
>>>>> James
>>>>

[toc] | [prev] | [next] | [standalone]


#12034

FromJames Martin <james@northwoodlumber.com>
Date2018-10-05 16:56 -0400
Message-ID<pp8j55$9l3$1@dont-email.me>
In reply to#12033
That's so. In Windows it locks up, in Linux it seems to go into an 
endless loop.

James

On 10/05/2018 04:37 PM, JohnMartens wrote:
> So calc won't open your file because it is to big ?
> 
> 
> Op 5-10-2018 om 21:48 schreef James Martin:
>> I don't have Excel but Libre Office opens the smaller files. Has there 
>> ever been a Visual Fox Pro RDD for VO?
>>
>> James
>>
>> On 10/05/2018 01:45 PM, JohnMartens wrote:
>>> I think Mathias question is: Can you open the file in Excel ?
>>> If so you can let Excel save the file as a format that you can read 
>>> in your App
>>>
>>>
>>>
>>> Op 5-10-2018 om 14:11 schreef James Martin:
>>>> No. I would like to generate reports regularly. Anyhow, if I can't 
>>>> open it I can't convert it to Excel.
>>>>
>>>> I have a hunch that the routine that reads in the whole record 
>>>> chokes at the ascii 198. The data comes in properly until the memo 
>>>> field; the fields after that are blank.
>>>>
>>>> James
>>>>
>>>> On 10/05/2018 02:43 AM, Mathias wrote:
>>>>> Is it a one time conversion? Try Excel.
>>>>>
>>>>> /Mathias
>>>>>
>>>>> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>>>>>> I am reading an unusual DBF via ODBC and the standard 
>>>>>> SQLSelect:GetData
>>>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The 
>>>>>> first
>>>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>>>> choke - at least I think so. The data is actually a reference to a 
>>>>>> memo
>>>>>> field and is 4 characters long. I don't need the memo field 
>>>>>> information,
>>>>>> but I do need all the other fields.
>>>>>>
>>>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>>>> then none of the rest of the record is read. The next record is 
>>>>>> read up
>>>>>> to the memo field again, and so on.
>>>>>>
>>>>>> I have tried to change the fieldspec for the field to Character(4) 
>>>>>> but
>>>>>> that does not work. I am fwriting information to a file and the
>>>>>> nODBCType is -1.
>>>>>>
>>>>>> Any ideas of what I could do?
>>>>>>
>>>>>> James
>>>>>

[toc] | [prev] | [next] | [standalone]


#12029

FromJames Martin <james@northwoodlumber.com>
Date2018-10-05 08:39 -0400
Message-ID<pp7m30$6t4$1@dont-email.me>
In reply to#12027
I can open the DBF with a program called "DBF Manager" and it opens it 
as a Visual Foxpro file. Will this help?

That program does not export the DBF as a VO compatible Foxpro file. It 
does not allow it to be exported in any other DBF format. DBAdmin does 
not open the DBF.

DBV Smart DataViewer opens the DBF but does not fill in the memo fields. 
This would work for me at this time. I would have to copy the required 
DBF out of the working directory so as not to conflict with the 
operation of the program. Since I just wan t to make reports for now 
this would work. How does DBV open this database since it is written in VO?

But what I really want to do eventually is to open it via the ODBC 
driver so my program works along with the other program through the 
server client architecture.

James

On 10/05/2018 02:43 AM, Mathias wrote:
> Is it a one time conversion? Try Excel.
> 
> /Mathias
> 
> Den torsdag 4 oktober 2018 kl. 23:20:41 UTC+2 skrev James Martin:
>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>> character of a memo field is ASCII 198 and this causes the routine to
>> choke - at least I think so. The data is actually a reference to a memo
>> field and is 4 characters long. I don't need the memo field information,
>> but I do need all the other fields.
>>
>> What happens is that SQLSelect:GetData reads up to the memo field and
>> then none of the rest of the record is read. The next record is read up
>> to the memo field again, and so on.
>>
>> I have tried to change the fieldspec for the field to Character(4) but
>> that does not work. I am fwriting information to a file and the
>> nODBCType is -1.
>>
>> Any ideas of what I could do?
>>
>> James
> 

[toc] | [prev] | [next] | [standalone]


#12031

From"Jamal" <noooospam@example.com>
Date2018-10-05 15:41 -0400
Message-ID<pp8ep5$i9m$1@news.albasani.net>
In reply to#12026
May be you can override the GetData() method and skip reading the field when 
you encounter the 198 ASCII value.

Jamal

"James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...

I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
character of a memo field is ASCII 198 and this causes the routine to
choke - at least I think so. The data is actually a reference to a memo
field and is 4 characters long. I don't need the memo field information,
but I do need all the other fields.

What happens is that SQLSelect:GetData reads up to the memo field and
then none of the rest of the record is read. The next record is read up
to the memo field again, and so on.

I have tried to change the fieldspec for the field to Character(4) but
that does not work. I am fwriting information to a file and the
nODBCType is -1.

Any ideas of what I could do?

James 

[toc] | [prev] | [next] | [standalone]


#12035

FromJames Martin <james@northwoodlumber.com>
Date2018-10-05 17:04 -0400
Message-ID<pp8jk7$d4g$1@dont-email.me>
In reply to#12031
I don't have a handle fo how it all works, but GetData does not seem to 
be the problem. It seems the data did not all get read it. Get data 
works for a few fields beyond the memo field, but theye are empty.

I would like to see the data Windows gets from the ODBC driver.

James

On 10/05/2018 03:41 PM, Jamal wrote:
> May be you can override the GetData() method and skip reading the field 
> when you encounter the 198 ASCII value.
> 
> Jamal
> 
> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
> 
> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
> character of a memo field is ASCII 198 and this causes the routine to
> choke - at least I think so. The data is actually a reference to a memo
> field and is 4 characters long. I don't need the memo field information,
> but I do need all the other fields.
> 
> What happens is that SQLSelect:GetData reads up to the memo field and
> then none of the rest of the record is read. The next record is read up
> to the memo field again, and so on.
> 
> I have tried to change the fieldspec for the field to Character(4) but
> that does not work. I am fwriting information to a file and the
> nODBCType is -1.
> 
> Any ideas of what I could do?
> 
> James

[toc] | [prev] | [next] | [standalone]


#12036

From"Jamal" <noooospam@example.com>
Date2018-10-05 17:52 -0400
Message-ID<pp8meh$4gd$1@news.albasani.net>
In reply to#12035
May be the problem then in the ODBC driver. Which driver are you using?

Would this help https://www.devart.com/odbc/xbase 
They have a trial.

Jamal

"James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me... 

I don't have a handle fo how it all works, but GetData does not seem to 
be the problem. It seems the data did not all get read it. Get data 
works for a few fields beyond the memo field, but theye are empty.

I would like to see the data Windows gets from the ODBC driver.

James

On 10/05/2018 03:41 PM, Jamal wrote:
> May be you can override the GetData() method and skip reading the field 
> when you encounter the 198 ASCII value.
> 
> Jamal
> 
> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
> 
> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
> character of a memo field is ASCII 198 and this causes the routine to
> choke - at least I think so. The data is actually a reference to a memo
> field and is 4 characters long. I don't need the memo field information,
> but I do need all the other fields.
> 
> What happens is that SQLSelect:GetData reads up to the memo field and
> then none of the rest of the record is read. The next record is read up
> to the memo field again, and so on.
> 
> I have tried to change the fieldspec for the field to Character(4) but
> that does not work. I am fwriting information to a file and the
> nODBCType is -1.
> 
> Any ideas of what I could do?
> 
> James

[toc] | [prev] | [next] | [standalone]


#12037

FromJames Martin <james@northwoodlumber.com>
Date2018-10-06 08:10 -0400
Message-ID<ppa8n6$o7t$1@dont-email.me>
In reply to#12036
The driver is OK. It is used by Crystal reports and it works without a 
hitch there. It is a special driver for use by a server/client 
architecture called codebase from Alberta Canada. The company no longer 
supports the product, which is unfortunate since it works extremely fast 
and we have no problems in the accounting program that uses it.

I expect that I will have to do some work to make it work, I already 
have to modify the numeric section of GetData to handle numerics which 
come across in base 16 instead of base 10.

James

On 10/05/2018 05:52 PM, Jamal wrote:
> May be the problem then in the ODBC driver. Which driver are you using?
> 
> Would this help https://www.devart.com/odbc/xbase They have a trial.
> 
> Jamal
> 
> "James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me...
> I don't have a handle fo how it all works, but GetData does not seem to 
> be the problem. It seems the data did not all get read it. Get data 
> works for a few fields beyond the memo field, but theye are empty.
> 
> I would like to see the data Windows gets from the ODBC driver.
> 
> James
> 
> On 10/05/2018 03:41 PM, Jamal wrote:
>> May be you can override the GetData() method and skip reading the 
>> field when you encounter the 198 ASCII value.
>>
>> Jamal
>>
>> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
>>
>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>> character of a memo field is ASCII 198 and this causes the routine to
>> choke - at least I think so. The data is actually a reference to a memo
>> field and is 4 characters long. I don't need the memo field information,
>> but I do need all the other fields.
>>
>> What happens is that SQLSelect:GetData reads up to the memo field and
>> then none of the rest of the record is read. The next record is read up
>> to the memo field again, and so on.
>>
>> I have tried to change the fieldspec for the field to Character(4) but
>> that does not work. I am fwriting information to a file and the
>> nODBCType is -1.
>>
>> Any ideas of what I could do?
>>
>> James

[toc] | [prev] | [next] | [standalone]


#12038

FromJames Martin <james@northwoodlumber.com>
Date2018-10-06 09:36 -0400
Message-ID<ppadp4$pdm$1@dont-email.me>
In reply to#12037
I've feel I've proven that it is the memo fields that cause the problem. 
When I copied the file to another directory, removed the memo fields, 
renamed the file and put it back to the original directory directory, it 
worked fine. I'll do that to another table just to be sure.

The next step will be to modify the sql program to ignore the memo 
fields and replace them with asterisks and label them character. This 
would work for me at this point. I think it will have to be done deeper 
in sqlselect than getdata.

James

On 10/06/2018 08:10 AM, James Martin wrote:
> The driver is OK. It is used by Crystal reports and it works without a 
> hitch there. It is a special driver for use by a server/client 
> architecture called codebase from Alberta Canada. The company no longer 
> supports the product, which is unfortunate since it works extremely fast 
> and we have no problems in the accounting program that uses it.
> 
> I expect that I will have to do some work to make it work, I already 
> have to modify the numeric section of GetData to handle numerics which 
> come across in base 16 instead of base 10.
> 
> James
> 
> On 10/05/2018 05:52 PM, Jamal wrote:
>> May be the problem then in the ODBC driver. Which driver are you using?
>>
>> Would this help https://www.devart.com/odbc/xbase They have a trial.
>>
>> Jamal
>>
>> "James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me...
>> I don't have a handle fo how it all works, but GetData does not seem 
>> to be the problem. It seems the data did not all get read it. Get data 
>> works for a few fields beyond the memo field, but theye are empty.
>>
>> I would like to see the data Windows gets from the ODBC driver.
>>
>> James
>>
>> On 10/05/2018 03:41 PM, Jamal wrote:
>>> May be you can override the GetData() method and skip reading the 
>>> field when you encounter the 198 ASCII value.
>>>
>>> Jamal
>>>
>>> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
>>>
>>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>> character of a memo field is ASCII 198 and this causes the routine to
>>> choke - at least I think so. The data is actually a reference to a memo
>>> field and is 4 characters long. I don't need the memo field information,
>>> but I do need all the other fields.
>>>
>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>> then none of the rest of the record is read. The next record is read up
>>> to the memo field again, and so on.
>>>
>>> I have tried to change the fieldspec for the field to Character(4) but
>>> that does not work. I am fwriting information to a file and the
>>> nODBCType is -1.
>>>
>>> Any ideas of what I could do?
>>>
>>> James

[toc] | [prev] | [next] | [standalone]


#12039

FromJames Martin <james@northwoodlumber.com>
Date2018-10-06 12:39 -0400
Message-ID<ppaogl$rc7$1@dont-email.me>
In reply to#12038
I've done it with a second file and it works with the memo fields 
removed. So I need to verify that Windows indeed gives the whole record 
to VO. To do that...

James

On 10/06/2018 09:36 AM, James Martin wrote:
> I've feel I've proven that it is the memo fields that cause the problem. 
> When I copied the file to another directory, removed the memo fields, 
> renamed the file and put it back to the original directory directory, it 
> worked fine. I'll do that to another table just to be sure.
> 
> The next step will be to modify the sql program to ignore the memo 
> fields and replace them with asterisks and label them character. This 
> would work for me at this point. I think it will have to be done deeper 
> in sqlselect than getdata.
> 
> James
> 
> On 10/06/2018 08:10 AM, James Martin wrote:
>> The driver is OK. It is used by Crystal reports and it works without a 
>> hitch there. It is a special driver for use by a server/client 
>> architecture called codebase from Alberta Canada. The company no 
>> longer supports the product, which is unfortunate since it works 
>> extremely fast and we have no problems in the accounting program that 
>> uses it.
>>
>> I expect that I will have to do some work to make it work, I already 
>> have to modify the numeric section of GetData to handle numerics which 
>> come across in base 16 instead of base 10.
>>
>> James
>>
>> On 10/05/2018 05:52 PM, Jamal wrote:
>>> May be the problem then in the ODBC driver. Which driver are you using?
>>>
>>> Would this help https://www.devart.com/odbc/xbase They have a trial.
>>>
>>> Jamal
>>>
>>> "James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me...
>>> I don't have a handle fo how it all works, but GetData does not seem 
>>> to be the problem. It seems the data did not all get read it. Get 
>>> data works for a few fields beyond the memo field, but theye are empty.
>>>
>>> I would like to see the data Windows gets from the ODBC driver.
>>>
>>> James
>>>
>>> On 10/05/2018 03:41 PM, Jamal wrote:
>>>> May be you can override the GetData() method and skip reading the 
>>>> field when you encounter the 198 ASCII value.
>>>>
>>>> Jamal
>>>>
>>>> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
>>>>
>>>> I am reading an unusual DBF via ODBC and the standard SQLSelect:GetData
>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>> choke - at least I think so. The data is actually a reference to a memo
>>>> field and is 4 characters long. I don't need the memo field 
>>>> information,
>>>> but I do need all the other fields.
>>>>
>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>> then none of the rest of the record is read. The next record is read up
>>>> to the memo field again, and so on.
>>>>
>>>> I have tried to change the fieldspec for the field to Character(4) but
>>>> that does not work. I am fwriting information to a file and the
>>>> nODBCType is -1.
>>>>
>>>> Any ideas of what I could do?
>>>>
>>>> James

[toc] | [prev] | [next] | [standalone]


#12040

FromArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
Date2018-10-09 17:18 +0200
Message-ID<ppigrm$1g38$1@gioia.aioe.org>
In reply to#12039
I think that it is not the Mem2String. It can be also something 
different: Some ODBC drivers allow data reading correctly on a record 
only once and some ODBC drivers need the memo fields only as the last 
fields before all other.

Arne Ortlinghaus


James Martin wrote:
> I've done it with a second file and it works with the memo fields 
> removed. So I need to verify that Windows indeed gives the whole record 
> to VO. To do that...
> 
> James
> 
> On 10/06/2018 09:36 AM, James Martin wrote:
>> I've feel I've proven that it is the memo fields that cause the 
>> problem. When I copied the file to another directory, removed the memo 
>> fields, renamed the file and put it back to the original directory 
>> directory, it worked fine. I'll do that to another table just to be sure.
>>
>> The next step will be to modify the sql program to ignore the memo 
>> fields and replace them with asterisks and label them character. This 
>> would work for me at this point. I think it will have to be done 
>> deeper in sqlselect than getdata.
>>
>> James
>>
>> On 10/06/2018 08:10 AM, James Martin wrote:
>>> The driver is OK. It is used by Crystal reports and it works without 
>>> a hitch there. It is a special driver for use by a server/client 
>>> architecture called codebase from Alberta Canada. The company no 
>>> longer supports the product, which is unfortunate since it works 
>>> extremely fast and we have no problems in the accounting program that 
>>> uses it.
>>>
>>> I expect that I will have to do some work to make it work, I already 
>>> have to modify the numeric section of GetData to handle numerics 
>>> which come across in base 16 instead of base 10.
>>>
>>> James
>>>
>>> On 10/05/2018 05:52 PM, Jamal wrote:
>>>> May be the problem then in the ODBC driver. Which driver are you using?
>>>>
>>>> Would this help https://www.devart.com/odbc/xbase They have a trial.
>>>>
>>>> Jamal
>>>>
>>>> "James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me...
>>>> I don't have a handle fo how it all works, but GetData does not seem 
>>>> to be the problem. It seems the data did not all get read it. Get 
>>>> data works for a few fields beyond the memo field, but theye are empty.
>>>>
>>>> I would like to see the data Windows gets from the ODBC driver.
>>>>
>>>> James
>>>>
>>>> On 10/05/2018 03:41 PM, Jamal wrote:
>>>>> May be you can override the GetData() method and skip reading the 
>>>>> field when you encounter the 198 ASCII value.
>>>>>
>>>>> Jamal
>>>>>
>>>>> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
>>>>>
>>>>> I am reading an unusual DBF via ODBC and the standard 
>>>>> SQLSelect:GetData
>>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The first
>>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>>> choke - at least I think so. The data is actually a reference to a 
>>>>> memo
>>>>> field and is 4 characters long. I don't need the memo field 
>>>>> information,
>>>>> but I do need all the other fields.
>>>>>
>>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>>> then none of the rest of the record is read. The next record is 
>>>>> read up
>>>>> to the memo field again, and so on.
>>>>>
>>>>> I have tried to change the fieldspec for the field to Character(4) but
>>>>> that does not work. I am fwriting information to a file and the
>>>>> nODBCType is -1.
>>>>>
>>>>> Any ideas of what I could do?
>>>>>
>>>>> James

[toc] | [prev] | [next] | [standalone]


#12050

FromJames Martin <james@northwoodlumber.com>
Date2018-10-11 15:21 -0400
Message-ID<ppo7so$toq$1@dont-email.me>
In reply to#12040
This ODBC driver works in the accounting program, and the memo field is 
not last. I was busy the last day or two, but I am searching where I can 
see the actual raw record and then I may be able to bypass the memo 
field characters. Otherwise I will need to modify the SQL statement to 
not ask for them. Does anyone know where I can have access to the raw 
ODBC record before parsing?

James

On 10/09/2018 11:18 AM, Arne Ortlinghaus wrote:
> I think that it is not the Mem2String. It can be also something 
> different: Some ODBC drivers allow data reading correctly on a record 
> only once and some ODBC drivers need the memo fields only as the last 
> fields before all other.
> 
> Arne Ortlinghaus
> 
> 
> James Martin wrote:
>> I've done it with a second file and it works with the memo fields 
>> removed. So I need to verify that Windows indeed gives the whole 
>> record to VO. To do that...
>>
>> James
>>
>> On 10/06/2018 09:36 AM, James Martin wrote:
>>> I've feel I've proven that it is the memo fields that cause the 
>>> problem. When I copied the file to another directory, removed the 
>>> memo fields, renamed the file and put it back to the original 
>>> directory directory, it worked fine. I'll do that to another table 
>>> just to be sure.
>>>
>>> The next step will be to modify the sql program to ignore the memo 
>>> fields and replace them with asterisks and label them character. This 
>>> would work for me at this point. I think it will have to be done 
>>> deeper in sqlselect than getdata.
>>>
>>> James
>>>
>>> On 10/06/2018 08:10 AM, James Martin wrote:
>>>> The driver is OK. It is used by Crystal reports and it works without 
>>>> a hitch there. It is a special driver for use by a server/client 
>>>> architecture called codebase from Alberta Canada. The company no 
>>>> longer supports the product, which is unfortunate since it works 
>>>> extremely fast and we have no problems in the accounting program 
>>>> that uses it.
>>>>
>>>> I expect that I will have to do some work to make it work, I already 
>>>> have to modify the numeric section of GetData to handle numerics 
>>>> which come across in base 16 instead of base 10.
>>>>
>>>> James
>>>>
>>>> On 10/05/2018 05:52 PM, Jamal wrote:
>>>>> May be the problem then in the ODBC driver. Which driver are you 
>>>>> using?
>>>>>
>>>>> Would this help https://www.devart.com/odbc/xbase They have a trial.
>>>>>
>>>>> Jamal
>>>>>
>>>>> "James Martin"  wrote in message news:pp8jk7$d4g$1@dont-email.me...
>>>>> I don't have a handle fo how it all works, but GetData does not 
>>>>> seem to be the problem. It seems the data did not all get read it. 
>>>>> Get data works for a few fields beyond the memo field, but theye 
>>>>> are empty.
>>>>>
>>>>> I would like to see the data Windows gets from the ODBC driver.
>>>>>
>>>>> James
>>>>>
>>>>> On 10/05/2018 03:41 PM, Jamal wrote:
>>>>>> May be you can override the GetData() method and skip reading the 
>>>>>> field when you encounter the 198 ASCII value.
>>>>>>
>>>>>> Jamal
>>>>>>
>>>>>> "James Martin"  wrote in message news:pp6078$m99$1@dont-email.me...
>>>>>>
>>>>>> I am reading an unusual DBF via ODBC and the standard 
>>>>>> SQLSelect:GetData
>>>>>> uses Mem2String(pTemp,UILen) to pass the buffer to a string. The 
>>>>>> first
>>>>>> character of a memo field is ASCII 198 and this causes the routine to
>>>>>> choke - at least I think so. The data is actually a reference to a 
>>>>>> memo
>>>>>> field and is 4 characters long. I don't need the memo field 
>>>>>> information,
>>>>>> but I do need all the other fields.
>>>>>>
>>>>>> What happens is that SQLSelect:GetData reads up to the memo field and
>>>>>> then none of the rest of the record is read. The next record is 
>>>>>> read up
>>>>>> to the memo field again, and so on.
>>>>>>
>>>>>> I have tried to change the fieldspec for the field to Character(4) 
>>>>>> but
>>>>>> that does not work. I am fwriting information to a file and the
>>>>>> nODBCType is -1.
>>>>>>
>>>>>> Any ideas of what I could do?
>>>>>>
>>>>>> James
> 

[toc] | [prev] | [next] | [standalone]


#12103

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-11-05 18:47 +0100
Message-ID<4g01udtq8r87ppd6nqt612a3obdhten8g6@4ax.com>
In reply to#12050
Replying on message of Thu, 11 Oct 2018 15:21:59 -0400 from James
Martin:


Hello James,

Have you solved this problem in the meantime?

Otherwise if you like I can take a look at how to read the data here. 

We are transfering dbv to X# and maybe a critical thing works fine
which did not in the VO version?

Dick

[toc] | [prev] | [next] | [standalone]


#12104

FromJames Martin <james@northwoodlumber.com>
Date2018-11-05 13:00 -0500
Message-ID<prq0fd$rg9$1@dont-email.me>
In reply to#12103
I got busy, and will not be able to look at it for the next month. I 
don't have Vulcan, so X# will not work for me since I need to access 
DBFs. Otherwise I have a keen interest in X#.

I have discovered that it is the memo fields that make a problem. I just 
skipped them in the select command and I can read the database. It will 
take work to find out what is the problem, since the company that makes 
the ODBC driver is not giving support for several years. Regardless of 
that I need to read the files since that is the current accounting program.

James

On 11/5/18 12:47 PM, D.J.W. van Kooten wrote:
> Replying on message of Thu, 11 Oct 2018 15:21:59 -0400 from James
> Martin:
> 
> 
> Hello James,
> 
> Have you solved this problem in the meantime?
> 
> Otherwise if you like I can take a look at how to read the data here.
> 
> We are transfering dbv to X# and maybe a critical thing works fine
> which did not in the VO version?
> 
> Dick
> 

[toc] | [prev] | [next] | [standalone]


#12105

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-11-05 20:24 +0100
Message-ID<lp51udpnonbaqs0okghp9g5vbt8j40db6q@4ax.com>
In reply to#12104
Replying on message of Mon, 5 Nov 2018 13:00:11 -0500 from James
Martin:


 Hello James,

>I got busy, and will not be able to look at it for the next month. I 
>don't have Vulcan, so X# will not work for me since I need to access 
>DBFs. Otherwise I have a keen interest in X#.

Ok, X# will work without Vulcan in a few months...

>
>I have discovered that it is the memo fields that make a problem. I just 
>skipped them in the select command and I can read the database. It will 
>take work to find out what is the problem, since the company that makes 
>the ODBC driver is not giving support for several years. Regardless of 
>that I need to read the files since that is the current accounting program.


Did you give dbMax a try? There used to be a download option via
http://www.ebertonline.de/ which (now?) does not work; that download
would work for a few weeks. An alternative is
https://en.freedownloadmanager.org/Windows-PC/DBMax-Database-Editor.html
but I am not sure if this is reliable.

I sometimes create an export from Excel 2003 to DBF and more than once
something goes wrong which result in an extreme large field being
created. While several DBF programs crash on opening it, dbMax usually
does not. 

As you started your post with "I am reading an unusual DBF" dbMax may
be your solution?

Dick

[toc] | [prev] | [next] | [standalone]


#12106

FromJames Martin <james@northwoodlumber.com>
Date2018-11-06 10:50 -0500
Message-ID<prsd8o$63l$1@dont-email.me>
In reply to#12026
I had to do some work to read numbers. I think they were base 16 numbers 
and I had to make a custom SQLSelect:GetData() to read the numbers. To 
work with the databases I used a custom select statement that excluded 
the memo fields. To fix this right one would have to have the driver for 
the database which is accessed via ODBC and somehow interface with it.

James

On 11/5/18 5:47 PM, Johan Nel wrote:
> Hi James,
> 
> Sorry for jumping in so late, if I remember correctly, I don't think it 
> is the ODBC driver, it is something in the SqlSelect class.  Had the 
> same issue with trying to retrieve text/memo from MS-Access.
> 
> 
> On 2018/10/04 23:20, James Martin wrote:
>> I am reading an unusual DBF via ODBC and the standard 
>> SQLSelect:GetData uses Mem2String(pTemp,UILen) to pass the buffer to a 
>> string. The first character of a memo field is ASCII 198 and this 
>> causes the routine to choke - at least I think so. The data is 
>> actually a reference to a memo field and is 4 characters long. I don't 
>> need the memo field information, but I do need all the other fields.
>>
>> What happens is that SQLSelect:GetData reads up to the memo field and 
>> then none of the rest of the record is read. The next record is read 
>> up to the memo field again, and so on.
>>
>> I have tried to change the fieldspec for the field to Character(4) but 
>> that does not work. I am fwriting information to a file and the 
>> nODBCType is -1.
>>
>> Any ideas of what I could do?
>>
>> James
>>
> 
> -- 
> *Johan Nel*
> George, South Africa

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web