By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,479 Members | 1,622 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,479 IT Pros & Developers. It's quick & easy.

Using MSDE automated with code.

P: n/a
Hello,

I was wondering if anyone here has experience deploying MSDE database with
Access as the front end? My issue is this; I'd like to deploy an MSDE back
end on a remote machine that I may or may not be attending. I'd like the
program (or at least A program) to see if the instance of the database
(let's say ABC.mdf) exists, and if it does not, then create it or "attach"
it to the MSDE. It would be nice on top of that if I could (in code)
identify an MSDE running on the current machine, but one step at a time.

Any ideas how do to this?

Thanks!
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Br
Jozef wrote:
Hello,

I was wondering if anyone here has experience deploying MSDE database
with Access as the front end? My issue is this; I'd like to deploy
an MSDE back end on a remote machine that I may or may not be
attending. I'd like the program (or at least A program) to see if
the instance of the database (let's say ABC.mdf) exists, and if it
does not, then create it or "attach" it to the MSDE. It would be
nice on top of that if I could (in code) identify an MSDE running on
the current machine, but one step at a time.
Any ideas how do to this?

Thanks!

Are you using an ADP?

To check if an ADP is connected:

blnConnected = CurrentProject.IsConnected

To bring up the connection dialog:

DoCmd.RunCommand acCmdConnection

or perhaps the latest incantation of the Access "package and deployment
wizard" may do this? (ie. Office Developer or VB Tools for the Office
System it's called now?)
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #2

P: n/a
Hi Bradley,

I'm using XP, no ADP, just a straight Mde file I'm trying to deploy. The
thing is, I'd like to use the MSDE, but would like to know if anyone has
deployed one with the P&D wizard, (or anything else for that matter). I
would like to make sure the database is registered with the server, then
harvest the server / machine name (on start up at least) then make sure that
connections reference that server and database on start up. Right now I do
something similar with the Access back end (check for connection, if no
connection, prompt for database location...etc.).

Any help or references would be greatly appreciated.

Thanks!

"Br@dley" <br**@usenet.org> wrote in message
news:7F******************@news-server.bigpond.net.au...
Jozef wrote:
Hello,

I was wondering if anyone here has experience deploying MSDE database
with Access as the front end? My issue is this; I'd like to deploy
an MSDE back end on a remote machine that I may or may not be
attending. I'd like the program (or at least A program) to see if
the instance of the database (let's say ABC.mdf) exists, and if it
does not, then create it or "attach" it to the MSDE. It would be
nice on top of that if I could (in code) identify an MSDE running on
the current machine, but one step at a time.
Any ideas how do to this?

Thanks!

Are you using an ADP?

To check if an ADP is connected:

blnConnected = CurrentProject.IsConnected

To bring up the connection dialog:

DoCmd.RunCommand acCmdConnection

or perhaps the latest incantation of the Access "package and deployment
wizard" may do this? (ie. Office Developer or VB Tools for the Office
System it's called now?)
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.