Previous versions of CalCon have used a DBASE file type with a dbf extension. CalCon now uses a Paradox file type with a db extension. When I open the dbf files in CalCon, they load correctly. When I try to load the db files, they don't load and I get the following message:
File name is too long for a Paradox version 5.0 table.
File F:\Documents and settings\Jack Hidley\My spreadsheets\Car\Engine\log files\040314143114.DB.
I've tried changing the filename to be 8.3 compliant by shortening it, but that didn't help. Any ideas?
I'm using version 1.0A5 of CalCon, version 1.30A8 of CalEdit on an A9L.
Moderators: EDS50, cgrey8, 2Shaker, Jon 94GT
- Jack Hidley
- Regular
- Posts: 64
- Joined: Mon May 12, 2003 1:13 am
- Location: Danville CA USA
CalCon 1.0A5 datalog file i/o prob - logs path can't be long
Jack Hidley
Maximum Motorsports Tech Support
Maximum Motorsports Tech Support
-
shonut
- Tuning Addict
- Posts: 462
- Joined: Mon Sep 15, 2003 7:11 pm
- Location: Ingleside, Ontario, Canada
- Contact:
Re: CalCon 1.0A5 datalog file i/o problem
What version was the log recorded with?Jack Hidley wrote:Previous versions of CalCon have used a DBASE file type with a dbf extension. CalCon now uses a Paradox file type with a db extension. When I open the dbf files in CalCon, they load correctly. When I try to load the db files, they don't load and I get the following message:
File name is too long for a Paradox version 5.0 table.
File F:\Documents and settings\Jack Hidley\My spreadsheets\Car\Engine\log files\040314143114.DB.
I've tried changing the filename to be 8.3 compliant by shortening it, but that didn't help. Any ideas?
I'm using version 1.0A5 of CalCon, version 1.30A8 of CalEdit on an A9L.
Has BDE been loaded?
Regards,
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
- Jack Hidley
- Regular
- Posts: 64
- Joined: Mon May 12, 2003 1:13 am
- Location: Danville CA USA
-
shonut
- Tuning Addict
- Posts: 462
- Joined: Mon Sep 15, 2003 7:11 pm
- Location: Ingleside, Ontario, Canada
- Contact:
Please e-mail me one. I've never seen this before.Jack Hidley wrote:Josh,
Yes, BDE was loaded when I installed version 1.2 of CalEdit. I just looked in BDE administrator and I don't see any reference to Paradox .DB file types. The logs were all made in CalEdit 1.30A7.
Regards,
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
-
shonut
- Tuning Addict
- Posts: 462
- Joined: Mon Sep 15, 2003 7:11 pm
- Location: Ingleside, Ontario, Canada
- Contact:
Got them, they play fine, I've e-mailed you .csv's of the log that I created with CalCon 1.0V5.shonut wrote:Please e-mail me one. I've never seen this before.Jack Hidley wrote:Josh,
Yes, BDE was loaded when I installed version 1.2 of CalEdit. I just looked in BDE administrator and I don't see any reference to Paradox .DB file types. The logs were all made in CalEdit 1.30A7.
I'd try uninstalling as much as you can (leave 1.20 if you have to) and re-installing.
Regards,
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
- Jack Hidley
- Regular
- Posts: 64
- Joined: Mon May 12, 2003 1:13 am
- Location: Danville CA USA
Josh,
I tried uninstalling all of the STKR software plus BDE. I then reinstalled BDE, then 1.30A7, then 1.30A8. I still get the same error.
One other piece of information. I tried opening one of these Paradox datalog files with EEC Analyzer and got this error:
Error 09:DBase IV Connection Error
The connection was not valid. The Dbase file name 'EEC_Analyzer.mdb' can not contain number or underscores. Please rename the file and try again.
This sounds like there is some problem with BDE going on.
I tried uninstalling all of the STKR software plus BDE. I then reinstalled BDE, then 1.30A7, then 1.30A8. I still get the same error.
One other piece of information. I tried opening one of these Paradox datalog files with EEC Analyzer and got this error:
Error 09:DBase IV Connection Error
The connection was not valid. The Dbase file name 'EEC_Analyzer.mdb' can not contain number or underscores. Please rename the file and try again.
This sounds like there is some problem with BDE going on.
Jack Hidley
Maximum Motorsports Tech Support
Maximum Motorsports Tech Support
- Jack Hidley
- Regular
- Posts: 64
- Joined: Mon May 12, 2003 1:13 am
- Location: Danville CA USA
Josh,
I just spoke with Clint Garrity. He knew what the problem was. Apparently the complete length of the filename, including the path, can't exceed 65 characters with the Paradox files. I moved my log files to the root of the drive and they open correctly with both pieces of software.
This should probably be tagged and moved to the resolved issues section.
I just spoke with Clint Garrity. He knew what the problem was. Apparently the complete length of the filename, including the path, can't exceed 65 characters with the Paradox files. I moved my log files to the root of the drive and they open correctly with both pieces of software.
This should probably be tagged and moved to the resolved issues section.
Jack Hidley
Maximum Motorsports Tech Support
Maximum Motorsports Tech Support
-
shonut
- Tuning Addict
- Posts: 462
- Joined: Mon Sep 15, 2003 7:11 pm
- Location: Ingleside, Ontario, Canada
- Contact:
Clint mentiond that to me with reference to his own software, and now it all make sense. :)Jack Hidley wrote:Josh,
I just spoke with Clint Garrity. He knew what the problem was. Apparently the complete length of the filename, including the path, can't exceed 65 characters with the Paradox files. I moved my log files to the root of the drive and they open correctly with both pieces of software.
This should probably be tagged and moved to the resolved issues section.
Thanks!
Regards,
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
Joshua Teixeira,
SHO NUT Performance
TwEECer RT Reseller
www.shonutperformance.com
sales@shonutperformance.com
EEC Analyzer User - now with one-step WB-based MAF tuning
http://EECAnalyzer.webhop.net
Who is online
Users browsing this forum: No registered users and 9 guests