[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Microsoft SQL Server Support |
Notice: | Please Registar, Note #11 |
Moderator: | AMCUCS::BETTS |
|
Created: | Tue Aug 23 1994 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 382 |
Total number of notes: | 1233 |
343.0. "Access V2.0 and SQL Server V4.2.1" by CHEFS::EDWARDSD () Tue Feb 25 1997 08:55
Hi,
We've got an application running here in the U.K using VB4 on the client and
MS-ACCESS V2.0 on the file server (an Alpha/NT 3.5.1). Due to the number of
users now accessing the system, I feel that MS-ACCESS is not the right database
product for us and consequently we are looking at upsizing to SQL Server.
Unfortunately, the users also have a MS-ACCESS V2.0 database locally on their
PC in order to provide offline working capabilities. These "local" databases
have links to the database on the file server. As a result, I believe we
are restricted to using SQL Server v4.2.1. Now, I've heard mixed things
about this version of SQL Server. Can anyone here tell me if we would get
advantages in terms of improved locking and performance by moving to this
version, or do we really need to be looking at upgrading both the front and
back-ends to ACCESS V7.0 before upsizing ? The application uses ODBC connects
to RDB and RMS datastores. Can the upsizing tool, and SQL Server, cope with
these connections ? Is it likely that we will need to make coding changes
as a result of the new database format ?
Thanks,
Dave
T.R | Title | User | Personal Name | Date | Lines
|
---|