Hi,

I am using the ado.net data provider v1.07 Build 3.

I set up the connection string  as
     Type = "Local";
and then connect to the database.
I can use the EDBDataReader to read and display all the rows in the
selected table.

I then change the Type="Remote" - no other changes
The first row returned by the datareader is Null in each of the
fields, the remaining rows are all correct.
The Server is 1.07 Build 3, Unicode. It is pointing to the same
configfile as the local access.

What else do I need to change to go from Local access to Remote?

Regards

Robin Joseph

Should have added - using VS2008 on XP, but also tested on VS2005 on a Vista machine

regards

Robin

Robin Joseph <ng_dx@robdjos.com> wrote:

Hi,

I am using the ado.net data provider v1.07 Build 3.

I set up the connection string  as
     Type = "Local";
and then connect to the database.
I can use the EDBDataReader to read and display all the rows in the
selected table.

I then change the Type="Remote" - no other changes
The first row returned by the datareader is Null in each of the
fields, the remaining rows are all correct.
The Server is 1.07 Build 3, Unicode. It is pointing to the same
configfile as the local access.

What else do I need to change to go from Local access to Remote?

Regards

Robin Joseph

Robin,

<< I then change the Type="Remote" - no other changes The first row returned
by the datareader is Null in each of the fields, the remaining rows are all
correct. The Server is 1.07 Build 3, Unicode. It is pointing to the same
configfile as the local access. >>

Sorry for the delay in getting back to you on this.  I've reproduced the
issue and a fix will be available in build 4 either Tuesday or Wednesday.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Thanks - I will wait for the next build

Regards

Robin

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

Robin,

<< I then change the Type="Remote" - no other changes The first row returned
by the datareader is Null in each of the fields, the remaining rows are all
correct. The Server is 1.07 Build 3, Unicode. It is pointing to the same
configfile as the local access. >>

Sorry for the delay in getting back to you on this.  I've reproduced the
issue and a fix will be available in build 4 either Tuesday or Wednesday.

--
Tim Young
Elevate Software
www.elevatesoft.com

Robin,

<< Thanks - I will wait for the next build >>

Also, I almost forgot - the next build/release (it may have to be a release
due to some remote server call changes) will also include VS 2008 support
along with design-time integration for both VS2005 and VS2008.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I look forward to it - it will make things a lot easier (the design
time integration)

Thanks

Robin

On Tue, 5 Feb 2008 19:18:22 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Robin,
>
><< Thanks - I will wait for the next build >>
>
>Also, I almost forgot - the next build/release (it may have to be a release
>due to some remote server call changes) will also include VS 2008 support
>along with design-time integration for both VS2005 and VS2008.

Robin,

<< I look forward to it - it will make things a lot easier (the design time
integration) >>

It's step one and provides all of the server explorer and dataset designer
support for connecting to/displaying/querying databases and setting up data
adapters for inserts, updates, and deletes.  The next step is to start
integrating the ElevateDB Manager functionality into the IDE with DDL
operations for creating tables, etc. in the server explorer.

--
Tim Young
Elevate Software
www.elevatesoft.com