Skip to main content
K
kevredphysics
Inspiring
August 14, 2011
Answered

MS db Connection String using ASP VBScript and DW8

  • 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

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. .

2 replies

K
kevredphysicsAuthor
Inspiring
August 15, 2011

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_Winters
Lon_WintersCorrect answer
Inspiring
August 16, 2011

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
August 21, 2011

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
August 14, 2011

>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?

Lon_Winters
Lon_Winters
Inspiring
August 14, 2011

If you're using a recordset on a page, and viewing that page for testing purposes, sometimes you have to go back and "refresh" the recordset. This is simply opening it and reserving it, then upload the page again. I don't know if this is some sort of bug, but I've had to do it often after making a change to the database. . Also, there have been times when my recordset is based on a query, I've had to refresh the query as well.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices