CatoBase 6.1.1 Update

[Phillies1000]

Originally Posted by jcato

Well, someone else having the same problem entered a support ticket and attached their data files. On may machine, it worked fine. Can you guys having trouble send me your data files so I can see if they work for me or not?

I'm currently using 6.0 but, I can't get that version to work. When I try to create a database, I get the error: Multi-step operation generated errors. Check each status value.


When I installed 5.4, it said that I had more recent files then some of the ones included in the install and I was asked if I wanted to install them or not. I chose not to. Is that the cause of the problem I'm seeing? If not, does anyone else have an idea what might be causing it?

Will updating to 6.1.1 fix this problem?

Thanks for the support and work on this great utility.

[Phillies1000]

Originally Posted by Phillies1000

I'm currently using 6.0 but, I can't get that version to work. When I try to create a database, I get the error: Multi-step operation generated errors. Check each status value.


When I installed 5.4, it said that I had more recent files then some of the ones included in the install and I was asked if I wanted to install them or not. I chose not to. Is that the cause of the problem I'm seeing? If not, does anyone else have an idea what might be causing it?

Will updating to 6.1.1 fix this problem?

Thanks for the support and work on this great utility.

I changed my creation directory to history/backup (my league name) and it worked fine now. I think my path name was too long before.

[sharpmath]

Originally Posted by bronco6710

Same exact problem here, except it was 'Batting.Team' and in my second season

In regards to those of you having this problem, jcato just figured this one out, for me anyways.

My Regional Settings are set to English (Canada) which changes the display of the date. DD/MM/YYYY, instead of the English (United States) display of MM/DD/YYYY.

I changed my settings, and everything imported perfectly!

This also explains why my post season games always showed up so oddly!!

Thanks SO much jcato, CatoBase is as better as it ever has been!

[MidRaven]

Just tried that, still a no go. Thanks, though.

[Phillies1000]

Originally Posted by Phillies1000

I changed my creation directory to history/backup (my league name) and it worked fine now. I think my path name was too long before.

I just finished successfully using Catobase 6.1.1. I've never used this incredible utility (or it's earlier incarnations) before today. I'm a little bit overwhelmed by all the data I now have to wade through, but am excited by the possiblities. Thanks again for a great utility.

[RayofHope]

I'm getting all the way through the players A-Z in create html pages, but then everything goes haywire on the team registries.

3021 erros about BOF or EOF being true but the current record has been deleted (?) and then immediately following those error 55's saying the file is already open (even though CatoBase is all I have open).

[bronco6710]

Any progress with the 'Batting.Team' and 'Pitching. Team' run-time error?

Step 2, Generate HTML reports in OOTP, is no longer necessary. Instead of using the HTML files, CatoBase will now use the text files located in the League_News_Box directory under the league directory. If you have to redo a previous season and you only have the HTML files and not the text files, CatoBase will use the HTML files automatically.

So does this mean, if we want to use text files, we set the data directory to "League_News_Box" and if we want to use HTML, we set it the export directory?

[Nuk]

Originally Posted by sharpmath

In regards to those of you having this problem, jcato just figured this one out, for me anyways.

My Regional Settings are set to English (Canada) which changes the display of the date. DD/MM/YYYY, instead of the English (United States) display of MM/DD/YYYY.

I changed my settings, and everything imported perfectly!

This also explains why my post season games always showed up so oddly!!

Thanks SO much jcato, CatoBase is as better as it ever has been!

Thanks! That's what worked for me too.

All those Americans - trying to drag us frostbacks down!

Thanks Jeff for a great add-on.

[bronco6710]

Originally Posted by Nuk

Thanks! That's what worked for me too.

All those Americans - trying to drag us frostbacks down!

Thanks Jeff for a great add-on.

I envy you canucks right now.

I've had this occur in multiple franchises so I've had to stop all of them until I can figure this out

[SnowMan]

I use American dates and still get that same problem with "Field '(pick one)' cannot be zero length"

[jcato]

Originally Posted by bronco6710

Any progress with the 'Batting.Team' and 'Pitching. Team' run-time error?

There are 2 problems leading to the Batting(Pitching).Team cannot be zero length problem. The first can happen for people using a different date format than the US Standard. Changing the date format to M/d/yy will solve this problem. I have updated the program to be independent of the date format. I've tested it out my system by changing the date format and it has worked fine. So hopefully it will work for others.

The other problem is related to an error when reading the ltrans.txt file. The line after a trade is not being processed. In one example, a player was signed on 2/11, released on 4/19, and signed again on 6/12. But, his release on 4/19 didn't get added to the transaction table because it was immediately after a trade. So, in CatoBase it looked like was signed and then signed again without being released. This led to some blank teams and the above problem. This also has been fixed.

I just want to get a hold of some more of the league files that were having problems and make sure it works for those before posting an update.

Originally Posted by bronco6710

So does this mean, if we want to use text files, we set the data directory to "League_News_Box" and if we want to use HTML, we set it the export directory?

No. The Data Directory is where CatoBase creates the CSV files and copies the text files to. CatoBase knows to copy the files from the League_News_Box directory that it finds under the League Directory that you specify. CatoBase will automatically copy the text files when you import a season. 99% of the time, you don't need to change the Data Directory from the default.

If you want to redo a database and have the data files from previous seasons, those might include HTML files instead of the text files. CatoBase will still use the HTML files if the text files aren't available, so you're still able to redo a database if needed.

[bronco6710]

Originally Posted by jcato

There are 2 problems leading to the Batting(Pitching).Team cannot be zero length problem. The first can happen for people using a different date format than the US Standard. Changing the date format to M/d/yy will solve this problem. I have updated the program to be independent of the date format. I've tested it out my system by changing the date format and it has worked fine. So hopefully it will work for others.

The other problem is related to an error when reading the ltrans.txt file. The line after a trade is not being processed. In one example, a player was signed on 2/11, released on 4/19, and signed again on 6/12. But, his release on 4/19 didn't get added to the transaction table because it was immediately after a trade. So, in CatoBase it looked like was signed and then signed again without being released. This led to some blank teams and the above problem. This also has been fixed.

I just want to get a hold of some more of the league files that were having problems and make sure it works for those before posting an update.



No. The Data Directory is where CatoBase creates the CSV files and copies the text files to. CatoBase knows to copy the files from the League_News_Box directory that it finds under the League Directory that you specify. CatoBase will automatically copy the text files when you import a season. 99% of the time, you don't need to change the Data Directory from the default.

If you want to redo a database and have the data files from previous seasons, those might include HTML files instead of the text files. CatoBase will still use the HTML files if the text files aren't available, so you're still able to redo a database if needed.

Thank you so much for being so responsive to everyone's concerns and making sure they get the best of your great utility, it is greatly appreciated.

[garlasco]

I'm still having a problem with Batting(Pitching).Team cannot be zero length problem. I have my settings as US(english)

What can I do?

THanks

PG

[nestajones]

Originally Posted by jcato

There are 2 problems leading to the Batting(Pitching).Team cannot be zero length problem. The first can happen for people using a different date format than the US Standard. Changing the date format to M/d/yy will solve this problem. I have updated the program to be independent of the date format. I've tested it out my system by changing the date format and it has worked fine. So hopefully it will work for others.

You're talking about the date/time kept by your computer generally? how can you tell what format it is being kept in? When I open Date and Time under my control panels, it shows fields to adjust month, year, and date. but it's not clear to me what "format" it's in, or how i would change it.

The other problem is related to an error when reading the ltrans.txt file. The line after a trade is not being processed. In one example, a player was signed on 2/11, released on 4/19, and signed again on 6/12. But, his release on 4/19 didn't get added to the transaction table because it was immediately after a trade. So, in CatoBase it looked like was signed and then signed again without being released. This led to some blank teams and the above problem. This also has been fixed.

Hmm, I didn't notice what player I was on when I got the error, but I will try running it again to see where it got stuck.

Glad to see I'm not the only person getting this run time error.

[nestajones]

Ok, I'm getting this run time error "Field 'batting.team' cannot be a zero-length string" when importing stats when it is processing a player who was released on August 19 and I signed on August 20. So that seems similar to what other people mentioned when they got the same error. However, I have the newest Catobase update which supposedly would keep this from occurring. So what do I do? I don't want to delete the player, which someone apparently did to solve the problem.

[gmo]

I don't believe he has released the version yet that should fix this. I think he just meant that he had found the problem and addressed it.

Probably depends on your OS, but in XP to see your date/time settings:
Start >> Control Panel >> Date, Time, Language, Regional Options >> Regional & Language Options

[nestajones]

Hmm, I do have Windows XP, but all I see under control panels is "Date and Time," and I don't see anything in there for regional or language options. All I can do is change the date and time, change my timezone, and change the internet server with which my computer synchronizes its time.

[octones]

It's just under regional and language options.

[jcato]

Okay, forget that whole thing about the date format. While it will work, it will also create some nasty side effects because players will get different playerids than they got before. The CatoBase PlayerID uses the birthdate as part of the calculation. So for players with reversible birthdates, they are going to get new PlayerIDs. For example a date of 4/8 with the US format is April 8th, but 4/8 with the UK format is August 4th. A date like 12/13 is the same in both since there isn't a 13th month, it will always be December 13th.

Anyway, I think I have this all fixed, so if you use a different date format than M/d/yy or you use M/d/yy and are still having problems, just wait for the update.

Thanks

[SandMan]

I found that the ltran records are not being read on some players. The work around is simple.

Do the folowing:

1. After getting the error for zero length, go into CATOBASE program and delete the season that you just processed to clear the ACCESS Table.

2. Go into the ltran.txt file and find the line with the player that the program crashed on. Delete this line, go to the next date record (begins with a 6) and paste it onto that date.

3. Re-run the CATOBase program with the use importer and create text files not selected.

4. This will correct the record if another record causes a crash then just redo the above steps. This works fine and it takes only about 2 minutes to do and the program works fine.

It is important to delete the current year from the tables first before you edit the tran file and make sure that the run importer option is not selected...

I hope this helps until the fix is ready -

Jeff - I have verified that the record for the release is not always getting processed by looking at the access batting or pitching table to see if the splits are in the table. Also I noticed that the 4 times the program crashed the line in the trans file was a trade between my team and another followed by the release record on my team. I just moved the record to the next date and it worked fine......



Hope this helps -