Inspiring

Answered

MS db Connection String using ASP VBScript and DW8

Forum|Forum|14 years ago
August 14, 2011
2 replies
2036 views

Hi

My MS db has been working with DW8 followong my use of a connection string in connSci***.asp. My OS is Windows7. This has worked fine.

<%
' FileName="Connection_ado_conn_string.htm"
' Type="ADO" 
' DesigntimeType="ADO"
' HTTP="true"
' Catalog=""
' Schema=""
Dim MM_connSciWeb_STRING
MM_connSciWeb_STRING = "DSN=DSN_******"
%>

Now when I update the db and check that the new additional records have been added (and they have been) I can still only access the original records. When I retest the connection string I get the 404 error message.

Can anyone help?

Regards

Kevin

Server side applications

This topic has been closed for replies.

Correct answer Lon_Winters

Is the synopsis of your issue that bregent provided correct? Please clarify that for us. Connection problems are not uncommon. but they are fixable.the first thing I think you need to resolve is the error when you test the connection in DW. If you didn't change anything in the connection script, then that means something changed on the server with the DSN or DB file itself, as bregent said. Recheck all the server files, DB location and DSN with the path to the DB. You could try deleting the DSN and recreating it. I would also suggest to try a DSN-less connection. These have been widely used with Access databases for many years, so you should easily be able to find instructions with a quick Google search. .

K

kevredphysicsAuthor

Inspiring

Thanks for all of this guys.

Switch to another system. But at the moment, with lowish volume, I need to resolve this prob. Hope I can get some inspiration sometime.

Kev

Lon_WintersCorrect answer

Inspiring

Is the synopsis of your issue that bregent provided correct? Please clarify that for us. Connection problems are not uncommon. but they are fixable.the first thing I think you need to resolve is the error when you test the connection in DW. If you didn't change anything in the connection script, then that means something changed on the server with the DSN or DB file itself, as bregent said. Recheck all the server files, DB location and DSN with the path to the DB. You could try deleting the DSN and recreating it. I would also suggest to try a DSN-less connection. These have been widely used with Access databases for many years, so you should easily be able to find instructions with a quick Google search. .

K

kevredphysicsAuthor

Inspiring

Hi guys

Sorry for the very slow reply but I have been on route from Italy to Uk by car! Very taxing and long journey. Now back to the problem.

The problem has been solved. I had to look for where the db was located on the server and change the direction to the db in the root folder. Like many things, it is easy when you spot that a couple of letters are wrong.

Thanks again.

Kevin

B

bregent

Participating Frequently

>This has worked fine.

When did it stop working? What changes did you make?

MM_connSciWeb_STRING = "DSN=DSN_******"

Any particular reason you are using DSN rather than DSNless connections?

>Now when I update the db and check that the new additional records have

>been added (and they have been) I can still only access the original records.

Can you explain? How do you know the new records where added if you can't access them?

>When I retest the connection string I get the 404 error message.

How are you testing the connection?

K

kevredphysicsAuthor

Inspiring

Hi

I don't recall making any changes to make it stop working.

There is no particular reason I are using DSN rather than DSNless connections. It just was working. I had trouble connecting and this on one worked.

I have a look at the ms database using Core FTP LE.

I test the connection string with DW.

Hope this helps.

Kevin

Lon_Winters

Inspiring

>I have a look at the ms database using Core FTP LE.

Let me see if I understand the facts.

1) This is a remote database

2) You update the data using a server side script, and the updated data appears on the website

3) You retrieve the Access database but the new data is not in there

If those facts are correct, then the database you are updating is not the same one you are viewing locally. This is a common problem and I know I've run into it before. Someone else recently experienced the same thing in the DW forum and not sure if they ever resolved it. To start with, make sure you only have one version of the database on the remote server.

I'm sorry, but once again I feel compelled to make this declaration. Dump remote Access databases! There are so many web hosts nowadays who offer Windows hosting and MSSQL databases. It's very easy to transfer your Access data and very easy to manage. Create an Access project file with the ADP extension to connect to and manage the database just as if you're working in a regular Access file. The only downside is that the DB has to allow remote connections, which many do not recommend. However, some web hosts also offer online admin tools.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded