Devart Forums

Building project, breaks in this message:

[DCC Fatal Error] DBXDevartInterBase.pas(84): F2039 Could not create output file 'C:\Program Files (x86)\Devart\DbxIda\Source\DBXDevartInterBase.dcu'.

All new from scratch. Computer with windows 7 64, D2009 and DbxIda 2:50:20. However, the same installation on windows XP, works normally.
Any ideas?

This problem is arised because this directory is read-only.
To solve the problem remove the read-only attribute for this directory.

Ok, you're right. It worked.
Thank you very much.

A new question in the same event:
A small network with 4 computers: a win32 XP Home SP3, two win32 XP PRO SP3 and a win64 7 ULTIMATE.
If the server is hosted in XP, the network works normal,
If the server is on win64 7, the departures of coneccções XP PRO working properly, but since XP home, the connection is complete, however, does not turn the tables (when you try to open them).
However, with the IBExpert, access is full.
Note: Among the attempts, and reformatted reinstelei XP Home and nothing has changed.
Any ideas?

What error do you have when opening tables?

Excuse me for forgetting to inform the message.
"Error loading midas.dll."
I have a midas.dll the same folder as the executable and one in "\ windows \ system32".

Complementing ... added a copy of Win XP Pro (in dual boot), with everything exactly the same. So I could test on the same machine the behavior of Win Home and PRO. The Win PRO run normally (not complain of midas.dll).

Maybe Windows XP Home does not have some components required by midas.dll.

As I said at the beginning, XP Home has always been part of this small network, has always worked well (as both client and server both).
Now, with Win7 (64bit) and server is that XP Home does not work like Clint.
But the reverse, used XP home as the server, the Win 7 normally enter as a customer.
However, the intention is to use the Win 7 as a server

Please try to use the standard dbExpress driver to connect to Win 7 server and check if the problem still persists.

Resolved.
Excuse me for using this space. But is that really had not occurred to me of any need to register midas.dll. In this case, the record was required only in a computer (with Win XP HOME).

I am happy that this problem has been solved.