although the question might seem to be similar to other questions concerning this subject, I am afraid it is more complicated.
I try to run a program that I programmed a long time ago under win XP using Delphi 2005.
Now using Delphi 10.2.3 Toky, working with the same program, I get an error bdertl and intraweb 72 90 not found.
I simply deleted intraweb components.
When I also deleted bdertl the error remains.
In the program I use ADO compounds. I don't see any compound which might be from Paradox , BDE-
Can anyone help me to resolve the bdertl error?
Thanks
Thommy7571
Check if BDE/Intraweb related pas files are present in the uses list. For example Dbtables, bde.
Related
Can anyone throw any light on an apparent partial incompatibility between TLibImp in Delphi 7and Win7 64-bit? Or suggest a less long-winded work-around than the one below?
I realise D7 is a bit long in the tooth, btw, but otherwise its IDE seems to behave faultlessly in Win7, which I suppose is a testament to MS's efforts on backwards compatibility.
Looking into another SO question earlier, I tried to use it to import ActiveDS.Tlb from \Windows\SysWOW64 using Project | Import Type library, but got an "Error accessing the OLE registry" error. I got the same error trying the copy in System32. Trying to import ActiveDS.Dll from both places I got "Error loading type library" instead.
I tried all the things which people say in the MS communities to try (Run Delphi as Administrator, Disable UAC, etc) and which David Heffernan told me (correctly) that I needn't do when I ran into the "Error accessing the OLE registry" error when I mistakenly tried to import a type library into XE4 the wrong way.
Otoh, on Win7 64-bit, D7 imports the type library for Adobe Acrobat and many others without complaint.
I managed to work around the problem by importing the ActiveDS.Tlb using XE6 and editing out the unit namespace prefixes, fwiw.
Also, I seem to recall but can't currently find a fix for one of the supplied units (ComObj maybe) for D5/D7
to avoid getting this error when a Delphi application started up which was caused by something like a problem in the way the COM object factory was initialized. But unfortunately, unlike some of the other Delphi utilities like TRegSvr, the source for TLibImp isn't supplied
There's not much to say here. Type library importing is a recurring problem area. Sometimes old versions of Delphi will import the libraries when new versions will not. And sometimes vice versa, as you have encountered. The type library importer has bugs, that's the long and the short of it.
Your workaround is the most effective way to deal with such problems. There's no point submitting a QC report because the problem is fixed in the latest version.
Asking on this is a bit of a shot in the dark but we've exhausted all other options unfortunately.
Our software package's .exe file exposes a COM library which many customers use through VBA functions in their Excel spreadsheet.
One particular customer recently reinstalled Windows, and then upgraded their version of our software package and now get this error message when trying to import our exe into Excel as a COM reference: http://msdn.microsoft.com/en-us/library/office/gg264377.aspx
Has anyone ever seen this before? The software is made using Borland Delphi 7 but I'm not sure if that makes much of a difference.
Looking in registry our GUID for the COM library is there, with the correct file location. We've exhausted all our usual tricks for fixing weird symptoms with our software.
If anyone has any ideas or has seen this before in their own environment then help would be greatly appreciated!
As a wild guess I speculated that the client may have 64 bit Excel. That would not be compatible with your 32 bit COM server.
Apparently that wild guess proved to be accurate!
I seem to be having some problems with dbExpress in Delphi XE2. When I try to set the connected property of the Sqldataconnection to true I get an access violation at 000000000.
The same thing happens when I try to change the CommandText or Active Properties of the SqlDataSet.
This is my first time using these components as I am following along with some tutorials from a book that I have so it may very well be something I am going wrong but I'm not exactly sure at this point.
Any help is appreciated.
Thanks.
Well I found the reason for my problems. Apparently the dbexpress drivers needed to connect to any database besides interbase are not available in Delphi XE2 starter which is what I am using.
Thanks for the help.
I have an old application running BDE under Delphi 7, and have now bought Delphi XE. Can I expect big problems if I try to stick with BDE under Delphi XE? Or will converting save me time in the end?
Issue 2: I have seen some people trying to use the included Installaware installer to install BDE and a database alias etc, but I am not sure if anyone succeeded. Is it possible?
Rgds PM
As long as you stick to 32 bit applications, it will work. There is no BDE for 64 bit.
But as everybody and his mother will point out: The BDE has been deprecated years ago and sooner or later you will run into trouble. E.g. you might not be able to install it on Windows 7 or your customers might fail to do that.
We are currently in the process of moving away from it and it is a pain in the lower back because it has been used in so many utilities for too long and there isn't quite an alternative for it for accessing dbase tables.
Over the last few days we have seen random access violations being raised on Delphi 2006 using the ClientDataSet when loading an XML block but the errors disappear when using CodeGear 2007 rad Studio.
I have a strange feeling that this is going to come back and haunt us in the future.
So, how can I debug the xml load procedure for a clientdataset.LoadFromStream method?
I can see it is defined in dbclient.pas but I cannot seem to find the xml processing section.
JD
I don't know if you've tried this already, but it's entirely legal (and supported) to use the Delphi 2007 version of midas.dll with a Delphi 2006 application. Since Embarcadero did fix some DataSnap bugs in Delphi 2007, there is some possibility that the errors you are seeing are caused by a Delphi 2006 bug. It is worth a try to substitute the 2007 version of midas.dll with your Delphi 2006 application and see if the errors go away. It might not fix the problem, but it will save you a lot of trouble and frustration if it does.
it been a while since ive been on 2006 but if i remember right
turn on debug packages then you should just be able to step into it
As far as I know the LoadFromStream cannot be used to load XML files, the data in the stream should be in the internal format used by the client dataset. Try setting the XMLData property instead.