Welcome, Guest. Please Login.
05/14/25 at 08:33:56
News:
Home Help Search Login


Pages: 1
Send Topic Print
2008 August upgrade-couldnt create .99 files (Read 795 times)
Laura  D. Oliver
Active Member
*****




Posts: 985
Gender: female
2008 August upgrade-couldnt create .99 files
12/17/08 at 17:24:59
 
I knnow a new upgrade is due out anyday, but I decided to do the August upgrade because of my Year End Change.
 
I only ran into two issues:
1)  I have never had a test company.  When I gave the Utilty the option to create .99 files I was told that it couldnt copy the ISNUMBER.B to testdata. I backed up and chose to skip rather than continue.  I didnt even try to do a DOS copy.
 
2) The first time I attempted to run UT-K-D I got "an error has occured while trying to open BKGLTRANB.88: , then it said "another user has this file open file"which was not true.  I tried to run UT-K-D a second time and it ran flawless.
 
One day I would like to have a test company. but I dont think I really need the .99 files, although the instructions did say that users with Atypical dictionary structures are more likely to have problems. Everything appears to be running great.  If not --I will hear loudly from some folks tomorrow.
 
Merry Christmas!
 
Back to top
 
 

Laura D. Oliver
classic DBA since 1997
EVO on Amazon server as of 5-2022
DIXIE PRECISION INC.
Birmingham, Alabama
(205)- 841-8400

www.dixieprecision.com



Email WWW   IP Logged
Vman
Senior Member
****


If it ain't broke,
don't fix it

Posts: 460
Gender: male
Re: 2008 August upgrade-couldnt create .99 files
Reply #1 - 12/18/08 at 12:45:00
 
I had a similar problem in that the *.99 files had been deleted, so when you would run an EVO update, it would try to re-create them in the TESTDATA folder, but would grind away and error out on each file.  I skipped the process and everything worked fine, except when you ran the data backup program you got an error popup saying that a *.99 file could not be found.  Essentially, the system thought that there was a *.99 company when there was no data (ours is a conversion to EVO from DBA).
Since UT-I would not allow me to create a *.99 company again, I got around it by copying the B-files from my main company to the TESTDATA folder and then changing the extensions to .99, using a freeware program called Extension Renamer.  This took care of the errors.
 
Back to top
 
 

EVO-ERP 2022.2
Build 4/22/22
Actican Zen V14 SP2 Workgroup
Win7 64-bit and Win10 Pro
WWW   IP Logged
Laura  D. Oliver
Active Member
*****




Posts: 985
Gender: female
Re: 2008 August upgrade-couldnt create .99 files
Reply #2 - 12/18/08 at 13:55:21
 
Thanks, thats great to know!   I am not on EVO yet, but I may experience the same problem in Classic.  
 
This .99 file thing must be fairly common.  I saw in the archives where KELLOGS had the same problem on 9-11-2008.
Back to top
 
 

Laura D. Oliver
classic DBA since 1997
EVO on Amazon server as of 5-2022
DIXIE PRECISION INC.
Birmingham, Alabama
(205)- 841-8400

www.dixieprecision.com



Email WWW   IP Logged
NovaZyg
Administrator
*****


When all else
fails.. Read the
instructions.

Posts: 789
Gender: male
Re: 2008 August upgrade-couldnt create .99 files
Reply #3 - 12/18/08 at 14:15:57
 
It is not documented anywhere, but It seems the update procedure both Classic and Evo, and even Older version of DBA, expect there to be a CO. 99    
 
That said, we added to our update, the check for the company 99 and to move the B  and B99 in the places it thinks it is supposed to be.
 
for most people this has worked, but for some it caused the above errors.
 
 
 
Back to top
 
 

Allen Landry
Evo~ERP

EvoERP and DBA Classic always Beta's of the Latest versions.

WWW   IP Logged
Pages: 1
Send Topic Print