Error when running processing

Rod Caddy rcaddy at pro-set.com
Wed Oct 12 14:43:23 PDT 2005


Kenneth Brody wrote:
> Quoting Rod Caddy (Wed, 12 Oct 2005 08:36:45 -0500):
> [...]
> 
>>During that process I write back out to those open lookups and I get
>>an error that says the following:
>>
>>fpODBC exception trap
>>
>>Exception error in UpdateRecord
>>This Field Can Only Be 0 or 1
>>This Field Can Only Be 0 or 1
>>
>>State:S1000,Native:-3703,Origin:[Microsoft][ODBC Microsoft Access
>>Driver]
>>State:S1000,Native:-3703,Origin:[Microsoft][ODBC Microsoft Access
>>Driver]
>>
>>RetCode = -1(0xffffffff)
> 
> 
> Is there a field in this file that can only be 0 or 1, and what value
> are you trying to put into that field?
> 
> 
>>I click OK and I get this message:
>>
>>UpdateRecord for 'odbc_jrnl' failed: -1
>>
>>I press enter and then get a repeat of the same messages when it
>>continues the processing and tries to write to a different file
>>than it did the first time.
>>At the end of the processing I receive this message:
>>
>>Deleted key is not found
>>
>>Index = odbc_jrnl/index.A
>>key="ABC
>>    "
>>recno = 2802
>>tptr = 3, 397, 3, 1, 0
> 
> 
> Is index A built on a field that you changed when the update failed?
> 
> [...]
> 
>>I was under the impression that I could update not only the
>>Filepro files but the Access files for simple manipulation.
> 
> 
> You can.
> 
> 
>>Any suggestions would be greatly appreciated.
> 
> 
> filePro, of course, cannot do things that the ODBC source won't allow,
> such as putting a "2" into a field that only allows "0" or "1".
> 
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> 
> 
> 
Ok, Here is what I have discovered.  The first time that the message 
comes up I had a write statement on that line and I changed it to be 
specific for the file I wanted to write, which was not the ODBC file, 
and it worked until I get to an end or to a point where there is no more 
processing.  So I think I may have done this incorrectly.  The original 
access database form name is form_id_191449693 but when I try to connect 
to it I get "cannot connect to table".  I manually created a query 
called psj and it connects to it without error.  So should I be creating 
the query in my processing and then write back into the table with odbc 
objects?  My guess is that the error is coming from a something that 
does not like to be written back out in the file.  The only field that I 
am updating is a text field that is set to N and I am changing it to Y. 
  Thanks for your response.

-- 
Rod Caddy
Pro-Set Systems
rcaddy at pro-set.com


More information about the Filepro-list mailing list