I just got done going through a preliminary setup for this at my facility...
Tony's FE Updater seems to consist of 2 files:
StartMDB.exe
YourFileName.ini
Plus whatever FE Files are to be updated, but you're obviously allowed to
use those. StartMDB is a compiled executable, no VB required, no way to
change it into a virus. Actually, there's no required coding at all other
than notepad to edit the .ini file with the locations (and that doesn't
exactly deserve the title of 'Coding'), so I'm not sure why this would be an
issue with your IT people. In case you haven't found it, the link for Tony's
AutoFE Updater is below (I'm not sure what 2 you have found).
http://www.granite.ab.ca/access/autofe.htm
Perhaps you can follow the link to Tom Wickerath's instructions for use, and
inform yourself on the fact that this updater has been approved for use
within Boeing (see the reference links within Tom's file), and then use that
information, along with an educated argument on pros and cons of an automatic
updater, to try and convince you're IT people to allow the use of this
executable.
For the record, this can be used to update any set of files/applications,
not just an Access app. You're IT people may even decide to use it for their
own purposes as well. I mention Boeing here, because I do some work for
them, and while they are not *the* worst I've seen when it comes to strict
requirements to pass approvals of any sort, they are certainly up there in
the list. I would assume that it must be worth something when trying to
convince someone to let you use this executable.
--
Jack Leach
www.tristatemachine.com
- "First, get your information. Then, you can distort it at your leisure."
- Mark Twain
"Stephen sjw_ost" wrote:
> So I have learned that allowing multiple users to use a single frontend could
> be a bad thing due to possible file and/or data corruption. To that point I
> am going to be distributing my FE to each user and have it load to the
> desktop, or other general location.
> The problem I have is the 2 AutoFEUpdaters that are available online seem to
> be based on VB6. My company has removed all access to VB6, something to do
> with security or whatnot.
> I can only use the Visual Basic window that comes with Access, Excel, Word,
> etc... So, is there any examples of an AutoFEUpdater that is written
> stricktly in Regular Access VB? Can 1 Access Database auto update another
> Access Databases Forms/Reports/Modules and maybe even Linked Tables? Probably
> just the Forms more than anything else.
> I will be investigating this as VB6 is out of the equation for me.
> Any help on the matter is, as always, greatly appreciated.
> --
> Stephen
Similar Threads
