Board index » delphi » Path too long for Paradox

Path too long for Paradox


2008-02-15 12:34:53 AM
delphi174
Hi All,
I have a Delphi 2007 app that is barfing saying the path is too long
for this version of Paradox. The BDE version reports 5.2. I am using
SHGetSpecialFolderPath and the CSIDL to get the location of the all
user's data folder and creating folders below this for my writable
data. On one computer, instead of C:\Documents and Settings\All
Users, it uses C:\Documents and Settings\All Users.Windows. This
makes the path too long for Paradox.
Any suggestions? Is there a BDE setting that can fix this?
Thanks,
Steve
 
 

Re:Path too long for Paradox

It's called InterBase Desktop edition. :-)
Steve writes:
Quote
Any suggestions? Is there a BDE setting that can fix this?

Thanks,
Steve
 

Re:Path too long for Paradox

Steve writes:
Quote
I have a Delphi 2007 app that is barfing saying the path is too long
for this version of Paradox.
It sounds as if the table level is 4 or 5, which had a max path length
(IIRC) of 128 characters. You need to make the table Level 7 (there
was no 6). You can do it by restructuring the table and including one
of the Level 7 specific features or you can do it the way I did ...
I open the table using the Px7Table component from Reinhard Kalinke.
The information I have says the latest versions are available form
ourworld.compuserve.com/homepages/r_kalinke but I don't know
whether that is current (it's a long time since I downloaded it).
The component has a function "SetLevel" which allows the level to be
changed.
My code is ...
Px7Table1.Open;
Px7Table1.SetLevel('7');
Px7Table1.Close;
That then allows the longer paths. (I had to do this a lot when we
moved to XP and stored tables in the profile.)
Hope that helps,
... Joe
Member of the UK Developers Group
 

Re:Path too long for Paradox

"Steve" <XXXX@XXXXX.COM>píse v diskusním príspevku
Quote
Hi All,

I have a Delphi 2007 app that is barfing saying the path is too long
for this version of Paradox. The BDE version reports 5.2. I am using
SHGetSpecialFolderPath and the CSIDL to get the location of the all
user's data folder and creating folders below this for my writable
data. On one computer, instead of C:\Documents and Settings\All
Users, it uses C:\Documents and Settings\All Users.Windows. This
makes the path too long for Paradox.

Any suggestions? Is there a BDE setting that can fix this?

Thanks,
Steve
Hi Steve,
state that you are neither from USA, France, Germany or Great Britain
and I shall help you.
Roman
 

Re:Path too long for Paradox

"Roman Krejci" <info@nospam dot rksolution.cz>wrote ...
Post cancelled. Keep your political issues out of these groups.
--
Wayne Niddery - TeamB (www.teamb.com)
Winwright, Inc. (www.winwright.ca)
 

Re:Path too long for Paradox

Quote
state that you are neither from USA, France, Germany or Great Britain and
I shall help you.
a) what kind of attitude is that?
b) Joe already supplied the correct answer, 10 days ago.. it is a level 4 or
5 table..
Diamond Software Group
www.diamondsg.com/main.htm
Paradox Support & Sales
Diamond Sports Gems
www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Roman Krejci" <info@nospam dot rksolution.cz>writes
Quote
"Steve" <XXXX@XXXXX.COM>píse v diskusním príspevku
news:XXXX@XXXXX.COM...
>Hi All,
>
>I have a Delphi 2007 app that is barfing saying the path is too long
>for this version of Paradox. The BDE version reports 5.2. I am using
>SHGetSpecialFolderPath and the CSIDL to get the location of the all
>user's data folder and creating folders below this for my writable
>data. On one computer, instead of C:\Documents and Settings\All
>Users, it uses C:\Documents and Settings\All Users.Windows. This
>makes the path too long for Paradox.
>
>Any suggestions? Is there a BDE setting that can fix this?
>
>Thanks,
>Steve

Hi Steve,

state that you are neither from USA, France, Germany or Great Britain
and I shall help you.

Roman

 

Re:Path too long for Paradox

Quinn Wildman (CodeGear Developer Support) writes:
Quote
It's called InterBase Desktop edition. :-)

Steve writes:
>Any suggestions? Is there a BDE setting that can fix this?
Quinn, that is not funny, and totally inappropriate!
The BDE is still supported for local Paradox and dBASE tables.
Ironically, there's more peer support than there is support from
so-called "Developer Support."
Rick Carter
XXXX@XXXXX.COM
Chair, Delphi/Paradox SIG, Cincinnati PC Users Group
--- posted by geoForum on delphi.newswhat.com
 

Re:Path too long for Paradox

You seem to be very much in the minority since in the two weeks since
Quinn posted his (to me) humorous reply you are the only one who has
taken it for anything other than what it was.
Just what kink of support do you think CodeGear should be providing?
Tech Support still supports the BDE. There is still a BDE newsgroup for
peer support.
--
Bill Todd (TeamB)
 

Re:Path too long for Paradox

Bill Todd (TeamB) writes:
Quote
You seem to be very much in the minority since in the two weeks since
Quinn posted his (to me) humorous reply you are the only one who has
taken it for anything other than what it was.

Just what kink of support do you think CodeGear should be providing?
Tech Support still supports the BDE. There is still a BDE newsgroup for
peer support.
If I failed to see the humor, I guess it is because to me this seemed to be
the latest post of many over the years (not all from Quinn) saying "If you
want any help from me, you will have to convert your whole application to
Interbase." There are obvious cases where that is not a practical solution.
Actually, I am quite pleased with CodeGear for continuing to make sure BDE
apps will continue to work for local Paradox and dBASE tables. And I'm
waiting to see what this "BDE replacement" that the roadmap tells us is
coming in the next version of Delphi is all about.
Like many of us, I am not using the BDE for new development these days
(which is part of why I hadn't dropped by for a couple weeks), but I have
some old apps out there that are still in use that have never been
rewritten to use another database technology.
If I over-reacted, it is because I worried that Quinn's response might have
meant that there are some CodeGear staff who think that continuing to make
sure that BDE apps will run under new versions of Delphi is not important.
If I wanted to rewrite all my apps every time a new technology comes out,
I would be using Microsoft products. :)
Rick Carter
XXXX@XXXXX.COM
Chair, Delphi/Paradox SIG, Cincinnati PC Users Group
--- posted by geoForum on delphi.newswhat.com
 

Re:Path too long for Paradox

Rick Carter writes:
Quote
Like many of us, I am not using the BDE for new development these days
(which is part of why I hadn't dropped by for a couple weeks), but I
have some old apps out there that are still in use that have never
been rewritten to use another database technology.
Likewise. There will always be some clients who refuse to spend money
to fix something that is not broken.
Quote

If I over-reacted, it is because I worried that Quinn's response might
have meant that there are some CodeGear staff who think that
continuing to make sure that BDE apps will run under new versions of
Delphi is not important.
I am not concerned about that. Not running under a future version of
Windows is another story.
--
Bill Todd (TeamB)
 

Re:Path too long for Paradox

Rick Carter writes:
Quote
If I over-reacted, it is because I worried that Quinn's response might have
meant that there are some CodeGear staff who think that continuing to make
sure that BDE apps will run under new versions of Delphi is not important.
You seems to me you are under the impression that if something went
wrong with the BDE we would fix it. In the year 2000 we said that won't
happen. Can something we told you we won't work on 8 years ago be
considered important?
I do see how deploying InterBase Desktop isn't always a practical
solution always for using it instead of the BDE. I'd suggest that
the BDE replacement is SQL Blackfish. The reason I say this is it is
freely deployable local database engine for low end database solutions,
like those you would use the BDE for.
 

Re:Path too long for Paradox

Quinn Wildman (CodeGear Developer Support) writes:
Quote
You seems to me you are under the impression that if something went
wrong with the BDE we would fix it. In the year 2000 we said that won't
happen. Can something we told you we won't work on 8 years ago be
considered important?
dn.codegear.com/article/28688
"The BDE itself, minus SQL Links, is primarily designed to support Paradox
and dBase local tables. BDE local table support will continue to ship in
future Windows Delphi and C++Builder releases for the foreseeable future."
The way I read that, it still ships with the product, and it still should
work. And, in my experience, it does.
When Nick Hodges did his "30 Camtasias in 30 Days" (in 2006, IIRC) he
devoted one day to demonstrating the use of the BDE for database access.
Why would the Delphi Product Manager be doing this? Doesn't there seem to
be an implicit suggestion that it is still OK to use the BDE with local
tables?
Quote
I do see how deploying InterBase Desktop isn't always a practical
solution always for using it instead of the BDE. I'd suggest that
the BDE replacement is SQL Blackfish. The reason I say this is it is
freely deployable local database engine for low end database solutions,
like those you would use the BDE for.
Bill and I are just two of the many who have some complex, sophisticated
applications in use that use the BDE. It would not be trivial for us to
rewrite those applications for Interbase or Blackfish SQL.
When someone on these forums asks for a simple fix to keep a BDE app
running, they deserve a good clear answer, not sarcasm. If you don't have
something helpful to say, stay out of the conversation!
Rick Carter
XXXX@XXXXX.COM
Chair, Delphi/Paradox SIG, Cincinnati PC Users Group
--- posted by geoForum on delphi.newswhat.com
 

Re:Path too long for Paradox

Quote

The way I read that, it still ships with the product, and it still
should work. And, in my experience, it does.
It does and it may still be working in 20 years. OTOH, it may stop
working when MS shipps the next version of Windows.
Quote

Bill and I are just two of the many who have some complex,
sophisticated applications in use that use the BDE. It would not be
trivial for us to rewrite those applications for Interbase or
Blackfish SQL.
It would be a whole lot easier to port Paradox table apps to
Advantage.<g>
Quote

When someone on these forums asks for a simple fix to keep a BDE app
running, they deserve a good clear answer,
And the answer now is the same as it has been since 2000. All
development of the BDE has stopped. There will not be any fixes,
patches, upgrades or changes. If it does not work on some future
version of Windows then that is the end of it.
--
Bill Todd (TeamB)
 

Re:Path too long for Paradox

AMEN!!!
Bill Todd [TeamB] writes:
Quote
And the answer now is the same as it has been since 2000. All
development of the BDE has stopped. There will not be any fixes,
patches, upgrades or changes. If it does not work on some future
version of Windows then that is the end of it.

 

Re:Path too long for Paradox

Quinn Wildman (CodeGear Developer Support) writes:
Quote
AMEN!!!

Bill Todd [TeamB] writes:
>And the answer now is the same as it has been since 2000. All
>development of the BDE has stopped. There will not be any fixes,
>patches, upgrades or changes. If it does not work on some future
>version of Windows then that is the end of it.
You guys are preaching to the choir. :)
I'm in full agreement with the quote from Bill above. We all know there
will come a day when BDE apps no longer work, and that it will almost
certainly come long before that day comes for Interbase or Blackfish.
Did you miss the post where I said I am not using the BDE for new projects?
Still, there are plenty of cases where there are still BDE apps out there,
and nobody is ready to pay for a conversion and rewrite.
In such cases, "How can I keep this BDE app working a while longer?" is
a completely legitimate question. That question should be given the
answer it deserves. It should not be met with derision, or by "bullying"
the poster that (s)he should immediately do a conversion and rewrite.
That's where I think Bill Todd and many others treat their peers with
respect, and go out of their way to give what help they can. Quinn, I
still think you could learn something from paying attention to how Bill
and other TeamB members answer such posts.
Rick Carter
XXXX@XXXXX.COM
Chair, Delphi/Paradox SIG, Cincinnati PC Users Group
--- posted by geoForum on delphi.newswhat.com