Tim,

> ampersand (@) keep coming from in your connection strings ?

Ampersand is "&" symbol - "@" is Ampersat or Asperand (or just plain
"at")

Eryk

Hi,

I have attached a very simple project that will connect to a DBISAM ODBC
version 4 table using VS 2005 in C#

Hope this helps

Chris Holland

Eryk,

<< Ampersand is "&" symbol - "@" is Ampersat or Asperand (or just plain
"at") >>

Duh !  I think we've had this conversation before, actually.

--
Tim Young
Elevate Software
www.elevatesoft.com

Joao,

<< The at sign(@) is used by CSharp to accomplish an automatic scape for all
backslashs in the string, besides other uses. It makes my s, tring exactly
like yours. Actually, I was just trying to play here and there to see if I
could find any error beyond the OdbcConnection.  >>

Ahh, I figured it was something like that, but was too lazy (busy to
look it up.

<< I've tried more then hundred configurations without success. Just to make
sure, I tried exactly the way you mentioned above... same error. Ive tried
with different ODBC manager configurations (File DSN, User DSN, System DSN),
I ve even monitored the system to see if I could point out some error...
Nothing found. >>

Do you know how to turn on the ODBC logging in the ODBC Administrator ?
That's the next step - to see if anything is showing up in the ODBC log at
all.

<< I advice you to test your drive with the files I sent you. I am pretty
sure you wont be ableto connect. You will have more elements to point out
the error anyway. >>

Actually, the tables have nothing to do with the connection phase, so I
didn't actually need them.

--
Tim Young
Elevate Software
www.elevatesoft.com

 Thanks Chris  for sending me the code. I had the same problem with the
 code you send. I've tried with several other drivers, works properly.
 When I try with the trial version it crashs down. I've tried on windows 2003, XP sp2,
 Windows 2000. That's enough.


 It 's definitely the trial driver. I could put my software to work with the
 ADO.net version from context software.

 I will buy Context software, plus the ODBC driver, cause this is
 the only way to put my system to work. After everything is working
 I will try to use the full version of the ODBC again.


 BTW, I've monitored the odbc driver some days ago, the log says that
 there is an error, but it isnot that clear. I've decided to move forward
 with what I have.


 Thanks for your help.


Joao,

joao,

<< It 's definitely the trial driver. I could put my software to work with
the ADO.net version from context software. >>

There's absolutely no difference between the trial version driver and the
normal full version driver other than a nag dialog.  This is just a regular
application, correct ?  Not an ASP.NET application ?

<< BTW, I've monitored the odbc driver some days ago, the log says that
there is an error, but it isnot that clear. >>

Please don't be vague - what's the error in the ODBC log ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

joao,

<< It 's definitely the trial driver. I could put my software to work with
the ADO.net version from context software. >>

There's absolutely no difference between the trial version driver and the
normal full version driver other than a nag dialog.  This is just a regular
application, correct ?  Not an ASP.NET application ?

WIndows app.
It does not work this way. I connect my program to a access, sqlserver,
interbase....you name it , but your driver. So dont tell me it is my program.
It has two lines, just two lines to test the connection. Everythingelse works.


<< BTW, I've monitored the odbc driver some days ago, the log says that
there is an error, but it isnot that clear. >>

<Please don't be vague - what's the error in the ODBC log ?

I will have to do the tests again. Sorry, I am not going to do it, right now. It up to you
guys now.
I bought the driver today, had no other change. I will work with the server version.
Later I will see what I can do with the odbc. I am way behind with this. If I have time
I will send you the odbc log later this week. If you drop 3 lines in  of code in VS2005
you will find the problem.



--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Joao,

I was able to run your code from VS 2005.Net Express. I'm pasting it
exactly the way it was.
--------------

            OdbcConnection conn = new OdbcConnection(
            @"
                        DRIVER={DBISAM 4 ODBC Driver};
                        catalogName=c:\taxhouse;
                        ForceBufferFlush=False;
                        ReadOnly=false;
                        LockWaitTime=100;
                        LockRetryCount=15;
                        ConnectionType=local"
            );

            conn.Open();

--------------
I was using *trial* v4 driver as well and received a nag dialog.
The problem was it would not work in debug mode. If you're starting
it with F5 it will throw an exception for some reason (MDA thing).
However, if you run it using Ctrl+F5, then it works just fine.
Funny as it is, I was just lucky to press a wrong shortcut actually
I didn't try to go further and run a query, but I'm sure it should
work. This is worth of a note somewhere, I think.

Regards,
Michael



Joao Araujo wrote:
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:
>
> joao,
>
> << It 's definitely the trial driver. I could put my software to work with
> the ADO.net version from context software. >>
>
> There's absolutely no difference between the trial version driver and the
> normal full version driver other than a nag dialog.  This is just a regular
> application, correct ?  Not an ASP.NET application ?
>
> WIndows app.
> It does not work this way. I connect my program to a access, sqlserver,
> interbase....you name it , but your driver. So dont tell me it is my program.
> It has two lines, just two lines to test the connection. Everythingelse works.
>
>
> << BTW, I've monitored the odbc driver some days ago, the log says that
> there is an error, but it isnot that clear. >>
>
> <Please don't be vague - what's the error in the ODBC log ?
>
> I will have to do the tests again. Sorry, I am not going to do it, right now. It up to you
> guys now.
> I bought the driver today, had no other change. I will work with the server version.
> Later I will see what I can do with the odbc. I am way behind with this. If I have time
> I will send you the odbc log later this week. If you drop 3 lines in  of code in VS2005
> you will find the problem.
>
>
>

Michael Baytalsky <mike@contextsoft.com> wrote:

Hi Joao,

>I was able to run your code from VS 2005.Net Express. I'm pasting it
>exactly the way it was.
>--------------

>             OdbcConnection conn = new OdbcConnection(
>             @"
>                         DRIVER={DBISAM 4 ODBC Driver};
>                         catalogName=c:\taxhouse;
>                         ForceBufferFlush=False;
>                         ReadOnly=false;
><                         LockWaitTime=100;
>                         LockRetryCount=15;
>                         ConnectionType=local"
>             );

>             conn.Open();

>--------------
>I was using *trial* v4 driver as well and received a nag dialog.
>The problem was it would not work in debug mode. If you're starting
>it with F5 it will throw an exception for some reason (MDA thing).
>However, if you run it using Ctrl+F5, then it works just fine.
>Funny as it is, I was just lucky to press a wrong shortcut actually
>I didn't try to go further and run a query, but I'm sure it should
>work. This is worth of a note somewhere, I think.


   Thanks a lot for your effort on this. I figured this out after I installed
   the official driver and it worked fine. Unfortunately, I did not find this
   information before.


    I 've been working with Ado/ODBC for a long time, found a lot of problems
    , nothing like this. This is funny, computers always tease us with
    new challenges.

Regards,

Joao,

Michael,

<< I was using *trial* v4 driver as well and received a nag dialog. The
problem was it would not work in debug mode. If you're starting
it with F5 it will throw an exception for some reason (MDA thing). >>

I got the MDA error (managed code issue with the nag dialog) also with the
trial version, but it certainly wasn't the error that he was getting.

<< However, if you run it using Ctrl+F5, then it works just fine. Funny as
it is, I was just lucky to press a wrong shortcut actually I didn't try
to go further and run a query, but I'm sure it should work. This is worth of
a note somewhere, I think. >>

Well, I think I'm going to have to re-do the nag dialog since it doesn't
like it being shown in the initialization of the DLL with VS 2005.

--
Tim Young
Elevate Software
www.elevatesoft.com