• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1306
  • Last Modified:

Delphi + BDe X Windows 7

I have a network that the server is Windows 7.
And a system Delphi + BDE, I can only run one computer at a time, if I try to open the program on two computers simultaneously. I get the error message.
"Directory is controlled by other .NET File....."
I've tried
I have already put in folder and subfolder (not to be directly in C:)
I have already put as a virtual drive with subst command.
Already shared with "all"and with clearance to read and write
Already have disabled UAC
I've used the compatibility mode and set the BDEAdmin as administrator.
I always delete the files,Pdoxusrs.lck, Paradox.lck, Pdoxusr.Net
And always set up correctly the path, in the BDeAdim.
Because as I said, activating the program separately on  the computer server or the client computer, the program works normally.
But I can not run the program on two computers at once?
Can anyone help?
0
adrex
Asked:
adrex
  • 10
  • 5
  • 2
  • +3
1 Solution
 
epasquierCommented:
Here are a few comments I've read on the subject. They all say the same, with little differences, with different words.. You should find the one that speaks to you the more

* the server workstation *must* be mapped to the net file, and to any shared
data, using the exact same path/mapping.. not just "it resolves to the same
place".. it must be *exact*

* In BDE Administrator the NetDir property of the Paradox driver must be
exactly the same on every computer. The only exception is that the
drive letter can be different on the server computer. For example, the
NetDir path on the workstations might be M:\netdir where M is a mapped
drive to c: on the server and on the server the NetDir path could be
C:\netdir or M:\netdir.

* be sure that on all clients the path to the .net file is exact the same.
use the bdeadmin to control and adjust this.
be also sure that other apps, like database-desktop are also use this settings.
after the net-dir change the bde must be restarted (simple restart the workstation)
0
 
adrexAuthor Commented:
I appreciated your comment. But see,  the BDE I have installed in hundreds of networks, basic questions is no problem, really need something advanced, about BDE or networking with windows 7.
Thanks.
0
 
epasquierCommented:
I don't think there is a problem between BDE and Seven as a server, because BDE only need the file sharing capability of the network, and that hasn't changed much in seven. So if you are sure
a) the app is working when launched separately
b) the access rights on the server are OK
c) the BDE is correctly configured in each station
d) you used a TSession component in your application, not just directly the TDatabase and TTable or other datasets directly connected to the files (which is AFAIK the recommended usage for sharable access, if not mandatory) and it is correctly setup

then as far as I know, you should have no problem or you have overlooked something "basic"

check that :
http://stackoverflow.com/questions/5384006/bde-windows-7-and-uac
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
8080_DiverCommented:
I have already put in folder and subfolder (not to be directly in C:)
By that, do you mean that you have put the app AND the BDE on the local box or are you trying to use the BDE from the server?

As a passing observation, you really, really should NOT still be using the BDE.  It has been deprecated for years now and has known problems.  Similarly, you should not be using TTable components to access datas and should, instead, be using QUERIES>

 Is there a reason you have not converted to the Expres or ADO components?
0
 
epasquierCommented:
yep, I agree with Diver, BDE is way way out of the game now.
Converting the application to something else might look like a pain, but a necessary one
0
 
8080_DiverCommented:
And, actually, (having done it before) it isn't really all that big of a PIA if you choose the right database to convert to and you think through and plan the conversion.  Of course, part of the Pain Level is dependent upon, shall we say, the quality of the code. ;-)
0
 
adrexAuthor Commented:
I know I did not develop more with the BDE, ok.
I use now, Firebird with  Devart's drive.
But,this is an application, that needs to continue working,until I can do a migration.
And the only problem is Windows 7 is preventing access or share the 3 files of control from BDE, namely Pdoxusrs.lck, Paradox.lck, Pdoxusr.Net.
This is the point.
If you focus on this point, really help me.
Thanks.
0
 
Ephraim WangoyaCommented:

You already know Windows 7 is not allowing you access to the folders of the files (Pdoxusrs.lck, Paradox.lck, Pdoxusr.Net)

Find a way to run your program with admin rights. For a simple test, right click your program, and run as admin. If that's the problem, there is your starting point
0
 
adrexAuthor Commented:
Really, I have not abandoned this issue.
Because,  that the problem remains unsolved.
With all due respect, but most of the comments, only repeat the same things with other words, or suggest actions that I have written that were made.
Therefore, I believe that should be closed, not becouse was abandoned, but for lack of solution.
Tanks.
0
 
mlmccCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
adrexAuthor Commented:
Really, I have not abandoned this issue.
Because,  that the problem remains unsolved.
With all due respect, but most of the comments, only repeat the same things with other words, or suggest actions that I have written that were made.
Therefore, I believe that should be closed, not becouse was abandoned, but for lack of solution.
Tanks.
0
 
adrexAuthor Commented:
After all the search efforts and attempts.
I believe this problem has not really solution.
Thank you all.
0
 
adrexAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for adrex's comment http:/Q_27033294.html#35977080

for the following reason:

As I wrote, there is no solution to this problem yet
0
 
epasquierCommented:
IMO, the real answer to this question is
* Diver : #35746243 : BDE is deprecated
* Me : #35746469 : You'd better invest your time by replacing it in your applications with something better DAC-wise (Data Access Components), maybe take also the time to replace the underlying DB if you feel it necessary

Sad, I know, but True nevertheless
0
 
adrexAuthor Commented:
Great genius epasquier,  we all know that, from the start !!!!

The question and not about programming, but on the end user, how to configure in order to continue using a system that is ready, get the picture now?
Now !  if I go say  your answer for my hundreds of end users who are already using a system read and finished.
They would not understand anything.
But what they know is that.
When  buy a new computer with Windows 7 starts to give trouble !!!
Your  text don't have the target to  solve de problem of question.
It is quite elementary, my other newer systems no longer use the BDE.

I could simply do nothing, because when I sold, nor was there a windows 7 project.
But do not think right, and, but I have no interest in remaking this system that I sold to many years ago.
I think I should try to help them, if possible !

The issue here, is not to offer your greate and wise counsel, about what tools to use for programming.
But to help my end users !
Thanks!!
0
 
adrexAuthor Commented:
Most important.
Because I think this issue should not be deleted, bat closed.
Knowing that no exit solution, yet.

It can be very useful, too.
Think how many people can read this.
People who may have a system ready and closed,  that uses BDE.
To manage your small business.
They will know, that if you buy and begin using a simple computer with windows 7 will cause a big problem in your business.
They will know that they will have to migrate before the program, when they have to actually use the windows 7.
And they will have time to prepare for this !
0
 
epasquierCommented:
Great genius epasquier,  we all know that, from the start !!!!
You would not believe the amount of questions here from people that do not even know what they are  willing to achieve. I just can't take the obvious knowledge for granted, or I wouldn't be able to give satisfying answers for half of it.

The question is not about programming, but on the end user, how to configure in order to continue using a system that is ready, get the picture now?
I do get the picture. What YOU don't seem to get is that this kind of problems is BOUND to happen, with the rapid evolution of software. BDE is an old dog, designed to provide local DB. It's mechanism to allow kind of "server" ability through Windows network is a tweak at best. Seven is a much more secure OS than what existed when BDE was lastly maintained. IT IS DEPRECATED. NOT MAINTAINED. DECOMMISSIONED. OUT OF ORDER. Pick the one you prefer.
So, if you want a "tweak" solution for that, you need experts that are not Delphi Programmers. And I didn't see many "Windows Networking" experts on this question.

So.... We (I include Diver) tried to "solve" your problem the only way we can rely on. Which is not by telling you how to do what you THINK will solve your problem, but by telling you the other way that we KNOW it will solve the problem.
I guess this is the difference between an expert and a good technician : the former can say when the road taken is wrong and that it is time to go back and pick another one.

I think I should try to help them, if possible !
I didn't say you should discontinue your application. It is just that switching entirely of DAC components is about as simple as project-wide search-replace, and rewrite connection configuration and other little details that are specific.
That is, if you didn't do anything not so good in your code, and you choose the next-gen DAC suite wisely.
Then you will come to your current user and say that as of now, they have to use the new .exe for all platforms, and forget about BDE configuration. It will work in a snap, and I believe they will be relieved.

about changing the DB system in the same time, I would say you would merely have to write your last Paradox application, by making a tool that can convert (at least load) paradox tables into your new DB system. I would recommend FireBird for its flexibility (can be used as local or server DBMS, without changing the exe). But maybe such tools already exists.

And last, about the BUSINESS OPPORTUNITY to undertake such a work (which can, granted, take a while anyway on large applications - testing and all included). That is not programming expertise but I will try to give a piece of advice anyway.
a) do you know how many users need that fix ? or will in the future
b) do they pay for a maintenance fee for your application ?
* it's normal practice
* usual rate around 10-15% of total cost of development per year
c) will they really be mad if you discontinue an old application ? it's your right after all, it happens all the time in software arena.

So, depending on the answers, you might have a choice to make : is it worth it or not ? Only you can answer that
0
 
adrexAuthor Commented:
spasquier;
I develop a few years ago, with exactly the Firebird + Delphi Professional  + the  drive for dbExpress/Firebird  of Devart (cheap and good).

As for my old system, is a market that no longer interests me.
But still get someone who knows a way to fool the Win 7.
Thank you, and always worth a good  discussion.

0
 
adrexAuthor Commented:
The new answer of sparquier  value to the solution.
And I would like to chose this.
Thanks
0
 
steinonlineCommented:
I have had this same issue with BDE and Windows XP.  Two workstations running an app that get's data from a Windows 2K Advanced Server.  I am absolutely certain that the problem is NOT Windows 7.  You must use as TSession component.  Furthermore your "client" machines should point to EXACTLY the same path (on the server) for the paradox.net file.  Each machine's own BDE Administrator must be configured so that the local working directory is private to that machine.  This takes care of Paradox.lck.  On the server the Pdoxusrs.lck file will then work properly.  You will however find that when a particular recordset is in edit mode by one user that it will be locked to all other users at that time.

It is easy to blame Windows 7, and or the outdated BDE, but the truth is, that these old programs are out there, and they were expensive to write, and they have not reached the end of their useful lives just because other companies write new OS and development software.  So we MUST support them.  Applications cannot be rewritten simply because a "Better" more modern tool has been invented. Businesses that waste money on stuff like that don't usually last too long.

My advice to you is to get yourself a copy of the old Delphi Super Bible.  Everything you need to know about your issue is there.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 10
  • 5
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now