No problems with scan here !
Last edited:
- Status
No problems with scan here !
Thanks - will give it a go tonight
Hi
I have two question regarding data for TCE:
1: In EliteOCR when you've used it as a standalone tool you have the ability to Export the data to a CSV file, can these files be used to Import back into the TCE Access DataBase? I realise that I'd need to update Station information for each one imported. I can add the stations via TCE and not manage the db for that.
2: How dangerous/safe is it for me to edit the Access db file? I OCR'ed a station and I had two lots of Cargo in my hold that the station didn't buy or sell, but these items were OCR'ed and included with that stations data, can I delete these entries from the db? The problem as I see is that the StationPrices are tagged with sequential ID's and deleting those entries would leave a gap in that sequence.
I have two question regarding data for TCE:
1: In EliteOCR when you've used it as a standalone tool you have the ability to Export the data to a CSV file, can these files be used to Import back into the TCE Access DataBase? I realise that I'd need to update Station information for each one imported. I can add the stations via TCE and not manage the db for that.
2: How dangerous/safe is it for me to edit the Access db file? I OCR'ed a station and I had two lots of Cargo in my hold that the station didn't buy or sell, but these items were OCR'ed and included with that stations data, can I delete these entries from the db? The problem as I see is that the StationPrices are tagged with sequential ID's and deleting those entries would leave a gap in that sequence.
Last edited:
Hello again,
1. No, this is not supported by TCE.
2. Yes, you can edit the data by the following: identify the Good ID, identify the Station ID, find the entry for both at the StationPrices table, DONT delete, replace the SELL value with a 0 (zero).
3. Before doing this make a backup.
Last edited:
Thanks for the quick response, you're awesome and I'm going to donate you some beer money for this tool. Now when I'm flying between places I can look at information in the tool whilst I'm still in the game and don't have to look over to my second monitor, pure brilliance and keeps the immersion.
Yeah, I didn't think (1) was possible, but if you don't ask then you'll never know. With regards to (2) thanks for the info and yes I'll create a backup before I change anything then test it first before I make it my default db.
Thanks again.
An odd thing since I updated from 1.33 to 1.36 is all the panel sizes and positions are out. Previously they were perfect (1680*1050) but now I hav had to resize nearly all to 80% and reposition all of the left hand ones. Is it now optimised for a different resolution? ( I know it is for 1920x1080 but previously it was perfect on 1680x1050)
I also lost my entire database as I stupidly had the install in the ED folder and ED just wiped it on update
(confusion when linking it to the log file locations, I thought TCE had to go there too) my bad - I'll start fresh
I also lost my entire database as I stupidly had the install in the ED folder and ED just wiped it on update
(confusion when linking it to the log file locations, I thought TCE had to go there too) my bad - I'll start fresh
Last edited:
It's safe to edit the database tables _if_ you really understand what you're doing and understand how the foreign keys tie certain tables together, and keep any row deletes in sync across tables that point to each other this way. The big gotcha is that some tables will expect the index column values to start at 1, so if for example you try to manually remove entire stations from the two tables that deal with registered station data and aren't careful with re-sequencing the index values, you're likely to run into errors and crashes.
So it's safe to _experiment_ but ALWAYS make a backup copy of the TCE.mdb beforehand that you can revert to.
So it's safe to _experiment_ but ALWAYS make a backup copy of the TCE.mdb beforehand that you can revert to.
An odd thing since I updated from 1.33 to 1.36 is all the panel sizes and positions are out. Previously they were perfect (1680*1050) but now I hav had to resize nearly all to 80% and reposition all of the left hand ones. Is it now optimised for a different resolution? ( I know it is for 1920x1080 but previously it was perfect on 1680x1050)
I also lost my entire database as I stupidly had the install in the ED folder and ED just wiped it on update
V1.35 introduced a new panel control and a new database for it. You will find the new panel at the control menu. There you can adjust all positions and the zoom level too. All changes are saved in the panel.mdb at the DB folder. If all fits, as you wanted, make a backup of it, because every new full-version has the initial database included and overwrites your configurated too. With the backup, you can get your configuration, you adjusted once, back.
Same here. No way to run this because it relies on Excel to run it. Now, if we could get an exe version of it to run as a standalone app...Judging by the screenshots, if it's a virus, the effort alone should be rewarded
(apart from the +1 rep!)
Pity I only have OpenOffice right now, but will watch this thread.
You can try it for free with a trial of Office 365. If you like it, an Office 365 subscription is only $9 per month or $99 per year.
Thanks for reporting. I preparing an update for the evening, that deals with this problem and some others. This error comes, if you are moving the scrollbar and then clicking on a star system.
Last edited:
That worked a treat thanks. Just need to utilise what info there is in the database. Currently around the Sedia/Nzamnite/HR 6836 area.
That makes perfect sense - thanks for doing all this
I'll carry on without using that method of selecting the Exploration status.
I think I have a problem in Trade Scout too but I need to verify that and will report back later
That makes perfect sense - thanks for doing all this
I'll carry on without using that method of selecting the Exploration status.
I think I have a problem in Trade Scout too but I need to verify that and will report back later
Working also on a new Trade Scout panel, but that will come later, maybe next week. I will post a preview screenshot, when i came home.
I usually rename the TCE directory to back it up - then use the installer version. Then copy the panels.mdb from the DB folder in TCE into the new one from the old one. Then use the Import database in the options panel of TCE to get your old data back in from TCE.mdb which is also in the DB folder of your old version.
There may be a better way - others can confirm.
Other than this error (and the other TRADE SCOUT error I reported earlier), just reporting that 1.36a is generally working fine for me.
Only stars got imported, that are not in the 22k+ database.
Last edited:
- Status