Skip to content
← Customer Feedback for Devart

Delphi Data Access Components

Delphi Data Access Components is a line of DB connectivity solutions for such databases as: Oracle, Microsoft SQL Server, MySQL, InterBase, Firebird, PostgreSQL, SQLite, Microsoft Access, DB2, Sybase Advantage Database Server, Sybase Adaptive Server Enterprise, and other databases (using ODBC provider).

http://www.devart.com/dac.html

Delphi Data Access Components

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve our Delphi Data Access Components?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

243 results found

  1. Possibility to set options not just for each DataSet, but for the whole session

    Currently such options as FetchAll, QueryRecCount, and others can be set for each DataSet separately. If you need to change these settings, you need either to do it manually at design-time or set them in cycle for all DataSets at run-time.

    We may add an option to set these values for all DataSets for a connection. For example, if FetchAll is set to True for a connection, all DataSets in this connection will use this value. You need to set this property only for those DataSets, that must have different value of this option.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Common  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Forced sending queries to the server without parameters

    Queries may be with or without parameters:

    select *
    from test_table
    where id = :ID

    or

    select *
    from test_table

    However some database servers execute queries without parameters faster than the same queries with parameters. An option (for example, AllowParams) may be added; if this option is set to False, all queries will be sent to a server as text.

    45 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Common  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Save settings to the database as in an *.ini file or in registry

    Many applications use TiniFile or TRegistry for saving their settings. However sometimes one user can work on several workstations with his login and password. He wants to have the same settings on all of his workplaces, and that settings, saved on one computer, were available on other ones.

    To implement this feature we may add classes or components with interface similar to TiniFile or TRegistry that save data not on the local computer, but in a database.

    82 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Common  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 … 9 10 11 13 Next →
  • Don't see your idea?