Professional Tools Account Changer

[barbola]

Guess what! We just bought this amazing tool and can change all our GL accounts.

I tried it, and it doesn't work!

Has anyone else used this?

I created my text file with two columns (old account, new account) and validated it (no errors). When I click Modify, it should ask me to select the file, but it doesn't. It continues on and acts as if the changes are being made, but the TACHANGE table contains nothing, the final report output shows no accounts changed, and voila, the accounts have not changed.

thanks!

 

[jazgeek]

probably sent you the wrong version. I had that problem with changer for customers years back.



-----------
and they wonder why they call it Great Pains!

jaz

 

[jymm]

we use it all the time (and it is a fantastic tool), but I must admit - we hand key all of the changes in when we need to do a change

also use it for item numbers and would not be without it.

 

[barbola]

Well it turns out it's just being picky. My original excel sheet had headings and extra worksheets.

I made the changes in the tab-delimited (txt) file but it didn't seem to like that. I had to go back and change the Excel sheet, and re-save it as txt.

It is very slow however...15-20 minutes for under 100 accounts and I have to change thousands this weekend.

b

 

[RobertC22]

hi Barbola,

Its a great tool, but as you found the text file extension and format are very picky.

Some years ago I had to convert a customer with 90,000 accounts down to 60,000.
For those where it was a straight number change, those flew threw - less than 15 minutes.
For the remainder which were merging GL accounts, some with six years of history, I was getting as slow as only 100 an hour. On average, was getting 1,000 an hour merged.

I was having to do it in batches of up to 10,000 accounts, otherwise the transaction log on the SQL database grew too big. It does all accounts in the file in a single SQL TRANSACTION regardless of whether the database is set to simple or full recovery!

I would suggest you pre-expand the transaction log file for the database before starting the convert. You can shrink it afterwards. Based on the testing I had done on the conversion before doing it for real, I expanded by log file to 10 Gigabytes. This saved sql having to request from the operating system another 100Mb every few minutes.

It took almost three days to convert the 90,000 accounts, checking it every few hours.

------
Robert

 

[barbola]

So far so good. I did small batches. It didn't matter if I had ten accounts or 10,000 accounts, it took 15-20 minutes.

thanks.