Name Lookup of Enterprise Manager

Hello!
I have noticed a strange behaviour of Enterprise Manager (or every
program to connect to SQL Server; as in Visual Studio, Query Analyser
and ODBC-Connection Manager), which I cannot get sorted out.
I try to connect to an MSDE-Instance on a clients' Server. The Server
has, for our Maintenance, a dial-up connection with dynamic IP and
runs a service to keep the IP up-to-date, so we can access it by
servername.dyndns.org.
I can ping the server and I can connect to it in pcAnywhere (using the
dyndns.org lookup).
If I try to connect to the MSDE as servername.dyndns.org\Instance, I
get an error: Server not found: Connection.Open(Connect()).
Trying to make an ODBC-Connection gives some numbers on the error:
SQLState: 01000
Server Error: 11004
followed by
SQLState: 08001
Server Error: 6
I can connect to MSDE by using the IP a ping gave me,
1.2.3.4\Instance.
Username and Password must be correct, because a connection with
IP\Instance works fine for the IP looked up a second ago. So my
Question is: Why does Name-Lookup work for ping, work for pcAnywhere,
but not for sql server?
I wonder if someone can give a hint on that on... looking Google
Groups and Knowledge base for the last 2 hours wasn't helpful...
Thanks!Sorry, but since nobody answered, and I really need a little help
here, I *bumped* this one up again.

> Hello!
> I have noticed a strange behaviour of Enterprise Manager (or every
> program to connect to SQL Server; as in Visual Studio, Query Analyser
> and ODBC-Connection Manager), which I cannot get sorted out.
> I try to connect to an MSDE-Instance on a clients' Server. The Server
> has, for our Maintenance, a dial-up connection with dynamic IP and
> runs a service to keep the IP up-to-date, so we can access it by
> servername.dyndns.org.
> I can ping the server and I can connect to it in pcAnywhere (using the
> dyndns.org lookup).
> If I try to connect to the MSDE as servername.dyndns.org\Instance, I
> get an error: Server not found: Connection.Open(Connect()).
> Trying to make an ODBC-Connection gives some numbers on the error:
> SQLState: 01000
> Server Error: 11004
> followed by
> SQLState: 08001
> Server Error: 6
> I can connect to MSDE by using the IP a ping gave me,
> 1.2.3.4\Instance.
> Username and Password must be correct, because a connection with
> IP\Instance works fine for the IP looked up a second ago. So my
> Question is: Why does Name-Lookup work for ping, work for pcAnywhere,
> but not for sql server?
> I wonder if someone can give a hint on that on... looking Google
> Groups and Knowledge base for the last 2 hours wasn't helpful...
> Thanks!

My SQL application on Windows Mobile 5

Hi

My application :

On PC : Access application + Access DB
On PocketPC : Embedded Visual Basic 3.0 application + PocketAccess DB

I synchronise my DBs through ActivSync.

It runs good before Windows Mobile 5.

My customers asked me for new PocketPC with this application, so I bought some new PocketPCs : but as I see, syncronisation with Access is no more supported.

So what are my solutions ?

My customer wait for there PocketPC, so I need a quick solution, I don't want to rewrite all my application now.
My application run before WM5, so now I don't want to have to pay for a Visual Studio .Net, some SQL Server, etc ....

Please, what are the solutions that won't cost me more than the time that have already lost with this new Windows Mobile 5 ?

Jo?l

Joel,

You're at the end of the road with eVB. You are going to need to move your mobile application's code either to the .NET Compact Framework or use Visual C++ for Mobile Devices (in VS2005) to achieve Windows Mobile 5 compliance. I recommend using SQL Mobile for your on-device database as a replacement for Pocket Access. Sorry there isn't better news, but eVB and Access have reached the end of their support time horizon for current and future Windows Mobile platforms.

-Darren

|||
Ok Darren

So if I move my application to .Net et use SQL Mobile 2005 on my PocketPC, what do I need to synchronise my PocketPC's database (so SQL Mobile) and my PC Database ?
Which database on PC ?
Each PocketPC will have his own PC and his own database, and it have to run my application on Windows XP Home.
What solution for synchronisation ?

Thanks for your explanations

Jo?l
|||Any solution ?

Jo?l
|||

Joel,

SQL Mobile comes with two options for data synchronization, Remote Data Access and Merge Replication. Both of these require IIS as the broker or gateway through which this synchronization occurs. In your situation, you may want to write a simple synchronization method that detects when the device is connected and uses System.Data.SqlClient to synchronize between your device database and SQL Server 2005.

-Darren

|||Ok Darren, thks.

Is there a place where I can find some example of this method ?

My SQL application on Windows Mobile 5

Hi

My application :

On PC : Access application + Access DB
On PocketPC : Embedded Visual Basic 3.0 application + PocketAccess DB

I synchronise my DBs through ActivSync.

It runs good before Windows Mobile 5.

My customers asked me for new PocketPC with this application, so I bought some new PocketPCs : but as I see, syncronisation with Access is no more supported.

So what are my solutions ?

My customer wait for there PocketPC, so I need a quick solution, I don't want to rewrite all my application now.
My application run before WM5, so now I don't want to have to pay for a Visual Studio .Net, some SQL Server, etc ....

Please, what are the solutions that won't cost me more than the time that have already lost with this new Windows Mobile 5 ?

Jo?l

Joel,

You're at the end of the road with eVB. You are going to need to move your mobile application's code either to the .NET Compact Framework or use Visual C++ for Mobile Devices (in VS2005) to achieve Windows Mobile 5 compliance. I recommend using SQL Mobile for your on-device database as a replacement for Pocket Access. Sorry there isn't better news, but eVB and Access have reached the end of their support time horizon for current and future Windows Mobile platforms.

-Darren

|||
Ok Darren

So if I move my application to .Net et use SQL Mobile 2005 on my PocketPC, what do I need to synchronise my PocketPC's database (so SQL Mobile) and my PC Database ?
Which database on PC ?
Each PocketPC will have his own PC and his own database, and it have to run my application on Windows XP Home.
What solution for synchronisation ?

Thanks for your explanations

Jo?l|||Any solution ?

Jo?l|||

Joel,

SQL Mobile comes with two options for data synchronization, Remote Data Access and Merge Replication. Both of these require IIS as the broker or gateway through which this synchronization occurs. In your situation, you may want to write a simple synchronization method that detects when the device is connected and uses System.Data.SqlClient to synchronize between your device database and SQL Server 2005.

-Darren

|||Ok Darren, thks.

Is there a place where I can find some example of this method ?