One alternative would be to use MSDE (Access 2000), which is really SQL
"Lite". You stiil have stored procedures, triggers, views, etc -- you just
don't get the enterprise manager. Instead the DB is managed through an
Access interface.
Regards,
Chris Michl
----- Original Message -----
From: "Dana Larose" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 29, 2000 1:41 PM
Subject: A** Backwards Conversion :)
> I know this goes against all reason and common sense, but here is goes...I
> have a client who has an Access-based system, and wants to upgrade it to
SQL
> Server. However, he keeps a local installation on a laptop, so he can
demo
> his site to clients.
>
> After we move to SQL Server, he will still want the demo copy on his
> notebook. Since I can't justify his purchasing a license for SQL Server
> Enterprise for a laptop, I need to know if there is an easy way to convert
a
> SQL Server db to an Access file.
>
> I can probably avoid (or work around) using triggers or stored procedures,
> so I just need the db structure, data and relationships replicated.
>
> Dana Larose
> ColdFusion Monkey
> Canadian Web Design & Consulting Inc.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
