
Jet 2.5 & 3.5 on same machine
Yes, Jet 2.5 and 3.5 (and 3.0, for that matter) can all reside peacefully
on the same machine. The files have different names and will not affect
each other.
Microsoft SQL Server is used in real client-server setups. It costs lots of
money and runs from a Windows NT Server. Needless to say, it is not
"distributable" like Jet or DAO.
SQL Server is Microsoft's recommendation for oversize Microsoft Access
database setups. They offer a few "upsizing" tools to make the migration
simpler. But as we've discovered in my office... migrating isn't 1/10 as
easy as Microsoft makes it sound. For instance: No field or tablename in
SQL Server can contain a space in its name, which is perfectly legal in MS
Access. So, you've got to rewrite any static queries or code that uses your
old-style, "SELECT * FROM tblMyRecords WHERE [Log Date] = #1/1/98#".
--Philip
Quote:
> Can Jet 2.5 and 3.5 reside on the same development machine. Need to
> access 3.5 mdb's and 2,5 mdb's without converting the 2.5 mdb's.
> Also, what is the major diff. between Jet and SQL Server? Does SQL
> Server require run-time fees, etc. or can it be distributed with a app
> as Jet/DAO does?