Data Access to Advantage Database Server

Thread is closed for posting
2 posts, 0 answers
  1. Kevin
    Kevin avatar
    1 posts
    Member since:
    Jan 2014

    Posted 04 Feb 2014 Link to this post

    I am evaluating DevCraft to work with Advantage Database Server v10.0.  Prior to installing DevCraft, I installed the Advantage .NET Data Provider and successfully wrote a test Console program that connected to the Database, Read data, and Updated data.  However, I am having trouble creating a Data Access Class Library project choosing 'Populate from Database', choosing 'Advantage Database Server' as my backend, leaving Model name to the default, and then using the same connection string to 'Set Connection Manually'. 
    It appears to connect to the server, because if I enter the user id or password incorrectly I receive an ADS generated error code, however, once I do enter the connection string (what appears to be correctly), the new Domain Model Wizard either hangs on (Reading Schema) or gives me the following message:
        Unable to retrieve the database schema information.  Reason: Unable to obtain index column(s) information.  This can happen if no password is provided when connecting to a database that is created with a password.  Please provide a valid username and password for the connection.

    One concern I had was that I was using the wrong Driver from ADS.  I downloaded the 9.10 Data Provider from ADS and added to the GAC using gacutil.exe, however, had the same results once this was done.

    Does reading the schema require an adssys user id? 
    I'm admittedly a novice with these tools and with Visual Studio.  Any help would be appreciated.
  2. Thomas
    Thomas avatar
    590 posts

    Posted 05 Feb 2014 Link to this post

    Hello Kevin,

    what we are using in our test suite is similar to the following connection string:
    Data Source=\\servername\aaa\bbb\ccc\ddd.add;User ID=adssys;Password=XXX;ServerType=REMOTE;

    With this connection string we are performing our schema read tests, and so this works. I tried now with a freshly created user (no permissions changed), and got the same exception as you. I don't know yet if this is fixable or not, and so I would like to kindly ask you to use the adssys user to obtain the schema.

    OpenAccess ORM is now Telerik Data Access. For more information on the new names, please, check out the Telerik Product Map.
Back to Top