Re: Re: Re: Upgrading from early 8.4 to current 8.4 hall error
Julia Underwood
2-20-18
My latest tests have brought me to a theory on this.

If a database has phone numbers in it that are longer than the field, that is greater than 20, then the import fails and does not complete.
Earlier versions were tolerant of this. The message shows: Too long string during import.... but after a number of these the import fails.
I have increased the length of the telephone number fields in hal I did them one by one, until all the messages cleared and the import completed, almost, it still crashes very near the end. So the database is still not sound.
I am assuming that normalised telephone numbers or something else that may have changed to cause this.

I am now trying to reconfirm this in my other database, I am aware that they have some long values, these may be be in other fields, I will check
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Piotr Wycichowski
Hi, I checked option "Use External Mail Software" in setting "Mail and Conferences Settings" in module "Mail and Conferences". When I create an invoice email I have a ...
17:38 8 Aug 2025
Piotr Wycichowski
Hi, Is somebody experienced in necessary settings for successful connection to server using webclient. When I tried, I got warning in brower, that Web client settings for HTTPS is not setup. So I ...
12:59 21 July 2025