Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 691
  • Last Modified:

Update Autonumber field

I have a asp script which pulls a bunch of fields from a access database, one of the fields ia a autonumber field, its not direclty editible in access.

But from asp, I would like to be able to edit this field, I tried but I get the following error message :


[Microsoft][ODBC Microsoft Access Driver] Cannot update 'orderid'; field not updateable.

The reason why i want to update it is becuase my credit card processor does not accept duplicate orderid fields, for example if the cc did not go through the first time it will record the orderid, then for exmaple if i correct the cc numbers and process it again it will come back with a duplicate order recieved, so i thought i could change the orderid filed by adding a -1 in front of the exisitng orderid number and running a update query as follws :

strsql = "UPDATE [ORDER] "
Strsql = Strsql & "SET [orderid]=" & orderidnew & " "
 Strsql = Strsql & "WHERE [orderid] = " & orderid & ""

       datacon.Execute(strSQL)

howver it doesn't seem to want to update the filed since is a autonuber field... any workarounds with this.. i dont want to change the datatype to integer in access, it must remain autonumber, but using some script in asp, i need to be able to change it if needs be.

i am sure there is a way around this. For example

AUTONUMBER is 123,124,125,126

if i want i should be able to change 124 to 124-1 so :
123,124-1,124,126 and the next autonumber remains 127.

tks.

0
Ricky11
Asked:
Ricky11
1 Solution
 
amit_gCommented:
>>i dont want to change the datatype to integer in access, it must remain autonumber,

Then you can't update this field.

If you don't want the change the datatype of this field, you will have to change the workflow a little bit. Mark this created order as cancelled or some status so that you know that this was cancelled and create a new order with same values.

Another rather simple alternative is to add a new field in the order table. Make 0 as default in that field. Send the OrderId-ThisFiledValue to your CC processor as OrderId. So your most orders would become 123-0, 124-0, 125-0 and so on. For the orders that fail to charge the CC for any reason and you need to do it again, update this field to the next number i.e. 1 and then the OrderId sent to the CC processor becomes 125-1. IF that fails again, the next time increment this field again and the OrderId for Cc processor would then be 125-2 and so on. This way you will never have to update the OrderId and the CC processor would always see a unique OrderId.
0
 
Ricky11Author Commented:
i see interesting.


if i change the datatype to integer, then i would have to code the orderid to increment automaticly correct? dont think i want to to that. would require a lot of changes.

i could re-create the order but then in that case if the cc declines 3 times or 4 times there would be 4 dead orders in the system marked as cancelled, would be a waste of space in the long run.

i am looking in to your 3rd idea of adding a new field, and defaulting to zero.

Let me type outlound... Hmm... If carderror field = declined  then if submiting order again, change counter = counter + 1, then join the orderid field and the counter field together and pass this as the order id ...

okay sounds  like it could work.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now