Hello Gerald, I believe you spoke to one of our consultants and they were able to assist you with a script to reseed the indexes for the table InvNum and _btblInvoiceLines. The best route would be to upgrade to the latest Sage 200 Evolution version where the table data type has been changed from Int to BIGINT to cater for table record limitation on how data is handled.

Thank you for the script but its still giving the same issue.

Please advise urgently with any other possible solution.  The next AutoIndex now on InvNum is 104000000, do you think this might be a problem on version 7.00.174?

I have asked the consultant to organize and schedule a remote session with you to implement the fix with you. But best case is to upgrade as this will be a temporary measure.

Hi Marvin,

Thank you very much for your response, the client is due for upgrade but because of the customisation its going to take a month. We have to get them up and running now.

Did you come right with the fix we provided?

no we didnt, the consultant from SAGE did the fix with us and still couldnt fix the issue as well

Let me check with the team. Expect feedback through the consultant handling this case.

Ok, thank you.

Gerald - please advise if you managed to find a solution for this , we in same situation , there is no ways we can rush an upgrade to relsolve 

HI Rob. 

Gerald and I previously worked together and we did manage to find a solution to this. 
It required alot of modification to the system stored procedures.

The quickest fix is to upgrade the client to Version 10, but just like you, that was out of the question as our client had alot of customization to the database. 

DId you manage to resolve this query? 

Regards,

Hoosen Ally