P
Paul
For the past several projects, I have been using an Access 2000 .adp file to
create and manage the database on the remote SQL Server. It has worked very
well for me and is a very fast, simple way to take care of minor updates.
A new project is not going so well, though. No matter what I try, I can not
get a connection established. This project is on a server I do not control,
so I am having to work only with the information provided to me by the
admin.
Using an online admin tool provided by the server administrator, I am able
to log in and view the database and make edits via manually written SQL
statements. However, using the server name provided and the same login info,
I am unable to establish a connection through Access.
The admin also told me to use a file-based DSN connection in my ASP pages; I
have always used DSN-less in the past, and can not figure out why a DSN
would be required. Could there be any connection between this and not being
able to connect via Access?
Any suggestions or ideas would be appreciated.
Thank you.
Paul
create and manage the database on the remote SQL Server. It has worked very
well for me and is a very fast, simple way to take care of minor updates.
A new project is not going so well, though. No matter what I try, I can not
get a connection established. This project is on a server I do not control,
so I am having to work only with the information provided to me by the
admin.
Using an online admin tool provided by the server administrator, I am able
to log in and view the database and make edits via manually written SQL
statements. However, using the server name provided and the same login info,
I am unable to establish a connection through Access.
The admin also told me to use a file-based DSN connection in my ASP pages; I
have always used DSN-less in the past, and can not figure out why a DSN
would be required. Could there be any connection between this and not being
able to connect via Access?
Any suggestions or ideas would be appreciated.
Thank you.
Paul