No .Fill method in Data Adapter

I am developing a Smart Device project for my Symbol MC9000 Windows Mobile
handheld. I am trying to make a simple connection to a SQL server. My proble
m
is my Data Adapter object does not have a .FILL method as it always has in
normal C# desktop apps.
I also noticed I cannot do a dataadapter object.dispose() either (i.e da.
Dispose(); )
Am I missing something or is this development environment for mobile just
that limited?
The intellisense only shows the following methods/properties for the da
object.
.DeleteCommand, .InsertCommand, .RowUpdated, .RowUpdating, .SelectCommand,
and .UpdateCommand.
That all it lists. Do I need to install something maybe?
I have never done a mobile app so this is all new to me.
Any help would be greatly appreciated.
Below is some of the code I am developing just to make the connection.
David
// Connection String for MSSQL Server
string Connection_String = "Initial Catalog=WINSTSDB;Data
Source=DB2ML350;workstation id=Symbol_MC9000w;packet size=4096;integrated
security=SSPI";
// Setup SQL Connection object
SqlConnection dbConn = new SqlConnection( Connection_String );
// Create Data Adapter object with SQL statement.
SqlDataAdapter da = new SqlDataAdapter("SELECT * FROM RackTemp WHERE SID =
'" + strSidcode + "'",dbConn);
// Define a Data Table object
System.Data.DataTable WinstisTable = new DataTable();
try
{
// Pull in data into data table object named WinstisTable
conn.Open();
da.Fill( WinstisTable );
}
catch(Exception exc)
{
MessageBox.Show(exc.Message.ToString(),"Error",MessageBoxButtons.OK,
MessageBoxIcon.Exclamation);
}
finally
{
// Close connection
conn.Close();
}
Message posted via http://www.webservertalk.comDavid C via webservertalk.com wrote:
> I am developing a Smart Device project for my Symbol MC9000 Windows
> Mobile handheld. I am trying to make a simple connection to a SQL
> server. My problem is my Data Adapter object does not have a .FILL
> method as it always has in normal C# desktop apps.
>
You might be better off posting this to a csharp or adonet newgroup. It's
somewhat offtopic here, and you are less likely to get a response than you
would in a relevant dotnet group (all the .Net groups have the word "dotnet"
in their names).
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.|||I guess because it is about SQL Connectivity that it might apply here. I wil
l
post on DotNetForums.com to see if some may help me.
David
Bob Barrows [MVP] wrote:
>You might be better off posting this to a csharp or adonet newgroup. It's
>somewhat offtopic here, and you are less likely to get a response than you
>would in a relevant dotnet group (all the .Net groups have the word "dotnet
"
>in their names).
Message posted via http://www.webservertalk.com

NIC Teaming Issue

I have a cluster using adapter teaming and it seems that when the virtual
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
Just a shot, but did someone tinker with the routing table on that node?
You may want to run ROUTE PRINT on both nodes and compare them.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
I have a cluster using adapter teaming and it seems that when the virtual
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
|||I just love NIC teaming software - NOT!
Make sure you the latest driver. Check your settings against the working
machine, I am sure it's something simple.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
>I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||Try disabling the NIC teaming. If the problem goes away...I think you've
found the source of you issues.
Regards,
John
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||This might be of interest:
The use of NIC teaming on all cluster networks concurrently is not
supported. At least one of the cluster networks that are enabled for
internal communication between cluster nodes must not be teamed. Typically,
the unteamed network is a private interconnect dedicated to this type of
communication. The use of NIC teaming on other cluster networks is
acceptable; however, if communication problems occur on a teamed network,
Microsoft Product Support Services may require that teaming be disabled. If
this action resolves the problem or issue, then you must seek further
assistance from the manufacturer of the teaming solution.
(Windows 2000, Windows Server 2003)
Server Clusters: Network Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/pro.../clstntbp.mspx
Sincerely,
Anthony Thomas

"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>