If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > PC based Database Applications > Corel Paradox > Paradox 5.x - Edit AUTONUMBER Record

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-10-04, 10:31
mcaprio99 mcaprio99 is offline
Registered User
 
Join Date: Apr 2004
Location: US
Posts: 2
Paradox 5.x - Edit AUTONUMBER Record

I am in desperate need of help. I am using Visual Basic 6. I am trying to "EDIT" a record in a Paradox 5.x table. I have no problem adding, deleting. My problem is trying to edit in a table where there is an AUTONUMBER field.

I query the table for the record, I update the field I want...No problem. When I pull that record back up, the AUTONUMBER field has changed. It is not the same when I started the edit.

I linked the tables in access and try the same edit. As soon as I change the field and click TAB to save the record, all the fields say: #DELETED. When I close the table and reopen it, the record apprears with the modified field, and the AUTONUMBER field has changed. I need to modify the record without changing the AUTONUMBER field.

I have also noticed one thing. This problem does not happen on one computer. The computer contains the following (3) files when I try to modify the record that are loaded in memory (idapi32.dll, idpdx32.dll, and idr200009.dll) all Borland / Inprise library files. Can someone please help, this problem has been bothering me for over 2 weeks. I know if I was using a Borland Programming environment, I could do this no problem, but the whole project was started & written in VB and I need to get it to work in this environment.

--Mike
Reply With Quote
  #2 (permalink)  
Old 04-21-04, 06:35
Shores Shores is offline
Registered User
 
Join Date: Aug 2003
Location: Bologna - Italy
Posts: 209
This is probably a problem with the ODBC driver or ADO or the BDE.

You should try to update the ODBC drivers, the ADO and the BDE, that woyld probably solve the problem.

Bye!
__________________
The only failure is not trying to do it.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On