problems accessing updated database from .asp file

[kapil29]

hi everyone

I am new asp. I have already have this .asp file, where it selects data from a MS Access database. Now I updated the database by adding a few more records. Everything else is the same, but now when I place the updated database with the same name as the old in the same folder as the old one, and then changing the name of the old one. But then when I run the code it does not retrieve any records from the updated database. Can please help me out with this and let me know of things that I should consider.

The following is the connection string code:
ConnStr = "filedsn=D:/paperFileDB/abc.dsn"
ConnStr = ConnStr & ";DBQ=D:/paperFileDB/abc.mdb"
ocm.Open(ConnStr)
the dsn file and the database are stored in the same folder on the server.
VBScript is used in the asp file.
Thank you
Kapil

[jhardman]

hi everyone

I am new asp. I have already have this .asp file, where it selects data from a MS Access database. Now I updated the database by adding a few more records. Everything else is the same, but now when I place the updated database with the same name as the old in the same folder as the old one, and then changing the name of the old one. But then when I run the code it does not retrieve any records from the updated database. Can please help me out with this and let me know of things that I should consider.

The following is the connection string code:
ConnStr = "filedsn=D:/paperFileDB/abc.dsn"
ConnStr = ConnStr & ";DBQ=D:/paperFileDB/abc.mdb"
ocm.Open(ConnStr)
the dsn file and the database are stored in the same folder on the server.
VBScript is used in the asp file.
Thank you
Kapil

You have updated the .mdb file and not the dsn? That could definitely cause the problem. The dsn tells the database driver to which db it should connect. The dsn could link to the old db and update its reference when the old db was renamed. When you connect through ado, I think it just uses the dsn, and only checks for the .mdb if it doesn't have a dsn.

By the way, why did you need to save a new copy of the db? It seems to me like it makes more sense to save a back up of the original, and then update the original. Then you wouldn't have this silly problem with the dsn getting confused.

Let me know if this helps.

Jared