I have contacted the sales department several times the last weeks, but they never return an answer to me...
Actually this is the reason that I ask here what to do.
Search found 14 matches
- Mon 03 Jun 2013 22:35
- Forum: PostgreSQL Data Access Components
- Topic: Reading and writing geographic objects
- Replies: 27
- Views: 90766
- Mon 03 Jun 2013 14:08
- Forum: PostgreSQL Data Access Components
- Topic: Reading and writing geographic objects
- Replies: 27
- Views: 90766
Re: Reading and writing geographic objects
How do I get access to the current version of PgDAC?
I have a current subscription (bought on 22 April 2013), but I am only able to download 3.x versions?
Best regards
Thomas
I have a current subscription (bought on 22 April 2013), but I am only able to download 3.x versions?
Best regards
Thomas
- Fri 19 Apr 2013 11:20
- Forum: PostgreSQL Data Access Components
- Topic: Reading and writing geographic objects
- Replies: 27
- Views: 90766
Re: Reading and writing geographic objects
I know that the feature is not available in UniDAC. My question is if the feature is now available in PgDAC?
Regards,
Thomas
Is this feature added in the current version?AlexP wrote:We will investigate the possibility of adding ability to work with geometric objects directly in one of the next versions of PgDAC.
Regards,
Thomas
- Wed 17 Apr 2013 07:43
- Forum: PostgreSQL Data Access Components
- Topic: Reading and writing geographic objects
- Replies: 27
- Views: 90766
Re: Reading and writing geographic objects
I'm a very happy user of UniDAC, but now I need to handle and manipulate objects of GEOMETRY type in a PostgreSQL database, which is not possible using UniDAC.
Regards,
Thomas
Is this feature added in the current version?AlexP wrote:We will investigate the possibility of adding ability to work with geometric objects directly in one of the next versions of PgDAC.
Regards,
Thomas
- Sun 18 Jan 2009 20:47
- Forum: dbExpress driver for InterBase & Firebird
- Topic: Connection to 64 bit Firebird on Vista
- Replies: 1
- Views: 3315
Connection to 64 bit Firebird on Vista
Environment: Delphi 2007 / Delphi 2009 running on 64 bit Vista (x64).
I am trying to connect to a 64-bit Firebird 2.1 server running on the local computer, but it seems impossible.
Error message (translated from danish - may look a bit different in native english):
System.IO.FileNotFoundException: The file or assembly 'Devart.DbxIda.DriverLoader, Version=1.0.0.5001, Culture=neutral, PublicKeyToken=09af7300eec23701' was not found.
Using the dbExpress driver for Interbase supplied by CodeGear works ok, except that it does not fully support Firebird 2.1
Any hints or work arounds will be greatly appreciated
Best regards
Thomas
I am trying to connect to a 64-bit Firebird 2.1 server running on the local computer, but it seems impossible.
Error message (translated from danish - may look a bit different in native english):
System.IO.FileNotFoundException: The file or assembly 'Devart.DbxIda.DriverLoader, Version=1.0.0.5001, Culture=neutral, PublicKeyToken=09af7300eec23701' was not found.
Using the dbExpress driver for Interbase supplied by CodeGear works ok, except that it does not fully support Firebird 2.1
Any hints or work arounds will be greatly appreciated
Best regards
Thomas
- Tue 23 Oct 2007 20:04
- Forum: dbExpress driver for InterBase & Firebird
- Topic: Quoted names problem
- Replies: 1
- Views: 3925
Quoted names problem
I can not figure out how or where to tell the driver to use quoted names for accessing Stored Procedures, Tables, Fields and so on.
In the query designer in Delphi 2007:
When trying to select * from a table called e.g. "Table1", the generated SELECT statement reads SELECT * FROM TABLE1, and even if I modify the statement myself when using it in a table- og query-component, it is automatically overwritten, effectively making it impossible to use quoted table names.
I think it is only me not knowing how to do, since it is stated in the "history" description, that "Bug with UseQuoteChar extended option fixed" in version 2.00.3
In the query designer in Delphi 2007:
When trying to select * from a table called e.g. "Table1", the generated SELECT statement reads SELECT * FROM TABLE1, and even if I modify the statement myself when using it in a table- og query-component, it is automatically overwritten, effectively making it impossible to use quoted table names.
I think it is only me not knowing how to do, since it is stated in the "history" description, that "Bug with UseQuoteChar extended option fixed" in version 2.00.3
- Tue 08 May 2007 20:55
- Forum: InterBase Data Access Components
- Topic: Improper handling of quoted field names
- Replies: 3
- Views: 4576
It seems like the handling of quoted names have several problems:
Example 1:
Stored procedures with quoted names and quoted parameter names can not be called using the IBCStoredProc component: When the IBCStoredProc editor is envoked, you get this messagebox
---------------------------
Error
---------------------------
Dynamic SQL Error
Input parameter mismatch for procedure .
---------------------------
OK Details >>
---------------------------
Example 2:
In components having a "KeyGenerator" property, the quotes around the generator name must be placed manually, but the "KeyFields" property handles quoted names correctly, if Options -> QuotedNames are set to true.
Maybe it should be checked that quoted names are generally handled as expected
Best regards
Thomas
Example 1:
Stored procedures with quoted names and quoted parameter names can not be called using the IBCStoredProc component: When the IBCStoredProc editor is envoked, you get this messagebox
---------------------------
Error
---------------------------
Dynamic SQL Error
Input parameter mismatch for procedure .
---------------------------
OK Details >>
---------------------------
Example 2:
In components having a "KeyGenerator" property, the quotes around the generator name must be placed manually, but the "KeyFields" property handles quoted names correctly, if Options -> QuotedNames are set to true.
Maybe it should be checked that quoted names are generally handled as expected
Best regards
Thomas
- Sun 22 Apr 2007 21:34
- Forum: InterBase Data Access Components
- Topic: Improper handling of quoted field names
- Replies: 3
- Views: 4576
Improper handling of quoted field names
When using quoted field names (IBDAC 2.0, Firebird 2.0), all fields are quoted by the "SQL Generator", but it seems only partially to use correct casing when generating SQL statements based on a given SELECT statement
Example:
INSERT INTO "TableX"
("ID", "MAALID", "METODEID", "STATUSID")
VALUES
(:"Id", :"MaalId", :"MetodeId", :"StatusId")
should have been generated as
INSERT INTO "TableX"
("Id", "MaalId", "MetodeId", "StatusId")
VALUES
(:"Id", :"MaalId", :"MetodeId", :"StatusId")
Example:
INSERT INTO "TableX"
("ID", "MAALID", "METODEID", "STATUSID")
VALUES
(:"Id", :"MaalId", :"MetodeId", :"StatusId")
should have been generated as
INSERT INTO "TableX"
("Id", "MaalId", "MetodeId", "StatusId")
VALUES
(:"Id", :"MaalId", :"MetodeId", :"StatusId")
- Wed 01 Feb 2006 14:20
- Forum: Oracle Data Access Components
- Topic: OraDataSource and OraProvider advantages
- Replies: 4
- Views: 3437
- Wed 01 Feb 2006 13:53
- Forum: Oracle Data Access Components
- Topic: OraDataSource and OraProvider advantages
- Replies: 4
- Views: 3437
Please forgive that I am not sure I understand your answer correctly.challenger wrote:As to TOraProvider, it was implemented to avoid some problems that persist in Delphi 4 and 5. If you use older version of Delphi then there is no difference between TOraProvider and TProvider.
Does this mean that the recommended provider component in multitier applications is TDataSetProvider? (I think that TProvider is not included in recent versions of the VCL).
I am using Delphi 7 and 2006.
Best regards,
Thomas
- Wed 01 Feb 2006 11:07
- Forum: Oracle Data Access Components
- Topic: OraDataSource and OraProvider advantages
- Replies: 4
- Views: 3437
OraDataSource and OraProvider advantages
Could anyone point out if there is any advantage by using the OraDataSource and OraProvider components compared to the standard Delphi DataSource and DataSetProvider components? They appear to be quite similar.
I have bought the ODAC NET components, which does not include the component source, so I can not check it out myself.
Best regards
Thomas Vedel
I have bought the ODAC NET components, which does not include the component source, so I can not check it out myself.
Best regards
Thomas Vedel
- Thu 05 Jan 2006 10:29
- Forum: Oracle Data Access Components
- Topic: Problems with Delphi7/ODAC4.5 and Delphi2006/ODAC5.7 on one machine
- Replies: 12
- Views: 5317
The registry settings has been sent to ODAC support and are made unavailable for download.thvedel wrote:I have made the registry settings available for download at http://www.veco.dk/BDS40registry.zip
Additional info:
As at test, I have tried installing the ODAC components on another computer, running exactly same versions of Delphi (7 and 2006) and ODAC (5.55 and 5.7), with same result: When ODAC 5.7 is installed, BDS 2006 cannot load any more; the splash screen "dies" before BDS starts loading IDE packages.
Then I rolled back this "other" computer (using Ghost) to a state just before I installed BDS 2006, installed all "missing" Windows updates, installed BDS 2006 from scratch including update 1 and finally installed ODAC 5.55 (Delphi 7) and ODAC 5.70 (BDS 2006).
Everything worked
This is really, really confusing, since the "cured" computer ended up running exactly the same programs (including versions) as it did before the roll-back.
Still, the two computers (the one which is still not working and the "cured" computer) are running exactly same versions of all installed software (WinXP, Delphi 7, BDS 2006 and ODAC). Only difference: The computer which is still having the problem has a fresh installed XP SP2 patched up with all updates. Eventually BDS 2006 with update 1 and ODAC has just been in installed a couple of days ago.
Since the computer is freshly installed with everything, I have no old Ghost image of it, making it impossible for me to try the same "cure" that worked on the test-computer. And scratching it and re-installing everything from scratch wil take a horrible amount of time (a couple of days), so I prefer not to test if it makes any difference.
Best regards
Thomas
- Wed 04 Jan 2006 20:17
- Forum: Oracle Data Access Components
- Topic: Problems with Delphi7/ODAC4.5 and Delphi2006/ODAC5.7 on one machine
- Replies: 12
- Views: 5317
All personalities installed.challenger wrote:Please specify what personalities did you install
Performed a complete install, except for installation of Corba support for C++ Builder, which I am sure I will never need.
I have made the registry settings available for download at http://www.veco.dk/BDS40registry.zipchallenger wrote:and if it is possible export and send to ODAC support address your BDS\4.0 registry key (HKEY_CURRENT_USER\Software\Borland\BDS\4.0). This should help us to find the problem.
- Wed 04 Jan 2006 13:29
- Forum: Oracle Data Access Components
- Topic: Problems with Delphi7/ODAC4.5 and Delphi2006/ODAC5.7 on one machine
- Replies: 12
- Views: 5317
I have a problem that sounds similar
Delphi 7 with Update 1 and ODAC 5.55 works fine.
On same computer: BDS 2006 (Architect with update 1) Splash screen hangs after installing ODAC 5.7 beta for Delphi 2006.
BDS 2006 Update 1 installed prior to installation of ODAC 5.7 beta.
Re-installation of BDS 2006 Update 1 tried, but no difference
When removing ODAC 5.7 for Delphi 2006 (using Control Panel -> Add or Remove Programs), BDS 2006 works ok - but without ODAC
Any hints would be greatly appreciated.
Delphi 7 with Update 1 and ODAC 5.55 works fine.
On same computer: BDS 2006 (Architect with update 1) Splash screen hangs after installing ODAC 5.7 beta for Delphi 2006.
BDS 2006 Update 1 installed prior to installation of ODAC 5.7 beta.
Re-installation of BDS 2006 Update 1 tried, but no difference
When removing ODAC 5.7 for Delphi 2006 (using Control Panel -> Add or Remove Programs), BDS 2006 works ok - but without ODAC
Any hints would be greatly appreciated.