Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
slbmis
Starting Member
7 Posts |
 Posted - 2002-03-11 : 13:40:32
|
I had previously used Ms Access 95 as both a database and front end application, I now want to migrate the database to MsSql 7.0 and migrate the application to Ms access 2000 using a adp file (Ms access Project).The senario is that using access 95 to access the database you would use this syntax :dim db as DATABASEset db = currentdb......The problem is that now these syntaxes does not seem to work using a access Ms access 2000.  Thanks |
|
|
yakoo
Constraint Violating Yak Guru
312 Posts |
Posted - 2002-03-11 : 14:10:00
|
| I belive Access 2000 uses VB as your code base.Do a general search on the internet for Recordset, Connection, and Command objects. These will allow you to connect to a database |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-11 : 14:24:03
|
| The other issue is that the concept of "CurrentDB" doesn't really apply in that scenario. An Access Project can utilize multiple databases on multiple SQL Servers. The only way that CurrentDB would make sense is if the tables are linked into the Access file. Even if you did this, CurrentDB is a DAO object, not an ADO object. The closest analogy in ADO would be a Connection object.You should look at the Access 2000 help file, and possibly MSDN, because there is documentation in one or both that describes the differences between the older DAO model and the ADO model, and has guidelines on converting from DAO to ADO. |
|
|
|
|
|
|
Access 95 migration