FrontAccounting forum — Account Code to be define as int

Re: Account Code to be define as int

null@example.com (boxygen) — Sat, 09 Jun 2018 18:04:42 +0000

@poncho1234

Stack Over Flow natsort() solution worked like a charm. Thanks A Lot.

Re: Account Code to be define as int

null@example.com (poncho1234) — Sat, 09 Jun 2018 12:50:23 +0000

May not solve your problem as used for ordering, but could help:-

stack-overflow mysql order varchar field as integer not sure how you could use this to select next, but maybe you can?

More here @ DBA SE pad the front with zeros or use CAST

Another one here uses a different method to sort by length 1st... the article also mentions a php function natsort() which may be worth investigating

Re: Account Code to be define as int

null@example.com (boxygen) — Sat, 09 Jun 2018 07:45:00 +0000

Thanks @Joe,

Yes I understand, but Actually I needed a customization to automatically pick the Next Available Account Code for the Given Account Type. It worked Fine till Code 2899 but when it reaches 28100 it is not picking the next value 28101 because the order sequence of Varchar says 28100 is smaller than 2899.

Converting it to INT is working fine but I fear it may cause anomalies. Any Ideas?

Re: Account Code to be define as int

null@example.com (joe) — Fri, 08 Jun 2018 22:32:15 +0000

Hello @boxygen

Yes it will. There are many tables where there are references to the account number, so please do not change this. Why do you want to change from varchar to int. The reason for using varchar is how the account numbers are sorted and there might be a wish in some countries to have them alphanumeric.
In most serious accounting systems this variable is varchar.

Joe

Account Code to be define as int

null@example.com (boxygen) — Fri, 08 Jun 2018 18:30:44 +0000

In chart_master table if I change the data type of account_code field from Varchar to int, will it cause any anomaly in relationships with other tables?

I have kept all Account Codes as Integer