Access and MSDE

how to i can connect the access database and the msde server?
i try whit the "odbc databases" function of access 2000 but not work
sql state 01000
errore di sqlserver
10060 impossibile effettuare la connessione
sql state 08001
errore di sqlserver 17
sorry for my english... ;(
IgnazioC
hi Ignazio,
IgnazioC wrote:
> how to i can connect the access database and the msde server?
> i try whit the "odbc databases" function of access 2000 but not work
> sql state 01000
> errore di sqlserver
> 10060 impossibile effettuare la connessione
> sql state 08001
> errore di sqlserver 17
10060 is a timeout problem. Make sure that you don't have firewall issues
between the client and server. Even personal firewalls on the Server will
block this traffic by default.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||before it worked,but to the unexpected one it did not work more.
I have changed the name of the pc and all now it works.
why happens this? my name of the pc are "locked" on msde sever? as I
can unlock it?
|||hi Ignazio,
IgnazioC wrote:
> before it worked,but to the unexpected one it did not work more.
> I have changed the name of the pc and all now it works.
> why happens this? my name of the pc are "locked" on msde sever? as I
> can unlock it?
as regard MSDE by it self, there's no problem at all... this was a problem
with SQL Server 7.0/MSDE 1.0 but it is no longer the case...
you can have now problems regarding ie: the registration on Enterprise
Manager, and, re-registering servers on Enterprise Manager UI will solve EM
problems..
or, of course, net problems due to not resolved computer names for firewall
as well...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

about messges in microsoft sql express

:eek: :eek: :eek: :eek:
Msg 156, Level 15, State 1, Line 6
Incorrect syntax near the keyword 'contains'.
Msg 102, Level 15, State 1, Line 8
Incorrect syntax near ')'.

i am getting error messages like this.
I want to know what this message really
mean i.e list of messages corresponding to numbers......The SQL engine uses only the error numbers internally. Those are what the engine know about, and are how it complains about "bad code" that it receives from the SQL client. The error message displayed below the Msg line contains a description of the error in the current locale (in this case, essentially a human language like English, Spanish, French, etc).

The process of getting the text description is simply a table lookup, there's no "magic" associated with it. The table of error messages changes constantly, usually with every service pack.

-PatP|||they are stored in sysmessages:

select * from sysmessages where error in (102,156)

About Endpoints

When I constructed my endpoint:

CREATE ENDPOINT MyNewEndPoint
STATE = STARTED
AS HTTP
(
PATH = '/MyEndpoint',
AUTHENTICATION = (INTEGRATED),
PORTS = (CLEAR),
SITE = 'arkansas'
)
FOR SOAP
(
WEBMETHOD 'GetSession'
(NAME='MyDB.dbo.spGetSession'),
BATCHES = DISABLED,
WSDL = DEFAULT,
DATABASE = 'MyDB',
NAMESPACE = 'http://MyDB/MyEndpoint'
)

the site is hardcoded. But, when I'm getting ready to deploy I'll need the site to be my production site. Is there an easier way to accomplish this then to edit the script each time before delpoyment?

TIA,
Dave C.

Hi Dave,

I assume you have some kind of a setup script or procedure? If that's the case, you could do this:

(a) Create the endpoint always with the hardcoded script above

(b) Bootstrap a small script execution with an ALTER ENDPOINT statement. For instance use SQLCMD.EXE like this:

SQLCMD.EXE -E -S. -Q"ALTER ENDPOINT MyNewEndPoint..."

or -of course- you could simply create the endpoint this way.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

About Endpoints

When I constructed my endpoint:

CREATE ENDPOINT MyNewEndPoint
STATE = STARTED
AS HTTP
(
PATH = '/MyEndpoint',
AUTHENTICATION = (INTEGRATED),
PORTS = (CLEAR),
SITE = 'arkansas'
)
FOR SOAP
(
WEBMETHOD 'GetSession'
(NAME='MyDB.dbo.spGetSession'),
BATCHES = DISABLED,
WSDL = DEFAULT,
DATABASE = 'MyDB',
NAMESPACE = 'http://MyDB/MyEndpoint'
)

the site is hardcoded. But, when I'm getting ready to deploy I'll need the site to be my production site. Is there an easier way to accomplish this then to edit the script each time before delpoyment?

TIA,
Dave C.

Hi Dave,

I assume you have some kind of a setup script or procedure? If that's the case, you could do this:

(a) Create the endpoint always with the hardcoded script above

(b) Bootstrap a small script execution with an ALTER ENDPOINT statement. For instance use SQLCMD.EXE like this:

SQLCMD.EXE -E -S. -Q"ALTER ENDPOINT MyNewEndPoint..."

or -of course- you could simply create the endpoint this way.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.