Drew Wutka
DWUTKA at Marlow.com
Fri Mar 16 16:49:44 CDT 2007
Ah, I thought you were trying to push or pull data from AD. I've done that several times. (Like pulling phone numbers from an .mdb, into AD accounts, or recording AD information in an .mdb) I know what your CTO is talking about, but I don't see how it would work 'better'. From what you are saying, I take it you have an .mdb that is a Front End application, and that you are currently using a .bat file to copy a 'master copy' from the network over the local copy. There are two disadvantages to using a straight batch method. One, if it's a login batch file, so it is running irregardless, then the two disadvantages is that you are getting a lot of extra network traffic when someone logs in (depending on the size of the Front End), and you are also slowing down the log in process. A method using AD would help here, but there's an easier way. Instead of doing an update at logon, do an update/check when the app starts. An access .mdb can't write over itself, but it can shell out, in fact, I thought this list had a community 'update' utility out there, one that several people worked on.... Personally, I had one I made in VB, that updated a front end that was only used for a few months. It's not too hard to do though... Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doris Manning Sent: Friday, March 16, 2007 4:22 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Update a database using Active Directory We are trying to find a better way of pushing a front-end update out to users. The CTO thinks we can use Active Directory to do that rather than using a batch file process to check the network for an update. He believes we should be able to use Active Directory to push an update to all users. I have never heard of this approach so I'm looking for more info or pointers. Doris Manning Database Administrator Hargrove Inc.