Distributing the front end versus distributing a shortcut

[Remster]

I've created a split database that will be used by thirty or forty people in my organisation, probably no more than two or three at a time. My preference is to keep a single copy of the front end in a shared folder (so I can modify it without having to involve the users) and to distribute a shortcut to it. However, everything I read about split databases talks about distributing the front end itself. Why, if at all, is distributing the front end better than distributing a shortcut?

[Bulzie]

Less possibility of corruption, someone locking the copy on the network, etc. What I do is have a VB exe as the shortcut for users. What this exe does when they click is check to see if the specific appllication folder is created on their C: drive and if not it will create it(this is for first time users). Then it will copy the FE database from network folder to that specific folder on their C: drive, then I go find their version of MS Access on their PC and open the database. This way I can make a copy of the FE database to make changes, testing, etc. while the users continue to use the current version. And when my changes are done and it is ready, I just copy it over the live FE databse on the network. So next time the users click the exe shortcut, they will always get the latest version.

[Mickjav]

One user one copy of front end

[Remster]

Great advice from both of you. Bulzie, any chance you could share the file or your code?

[JoeM]

Bulzie's suggestion is definitely the way to go. I do something very similiar. If you have multiple users using the same copy of the front end simultaneously, that really defeats the purpose of splitting the database and can still run into the corruption issues.

Bulzie's suggestion gives you the benefits of running it from a shortcut, while gaining the benefits of everyone having their own copy, to avoid corruption. And you don't have to worry about rolling out changes/new versions to users. It is seemless, and doesn't require any extra effort on the part of you or users.

[isladogs]

Absolutely. Never allow users to share the same copy of the FE. You will definitely get corruption at some point.

The only difference in my approach is that the desktop shortcut is to a starter app which looks like a splash screen.
This checks whether a newer version is available on the network.
If so, that is first downloaded before the main app is opened and the starter app quits automatically.
Again it is seamless and end users are not aware how it works
I use that approach rather than download a fresh copy of the FE every single time the app is run.
This makes the startup time much faster

[Bulzie]

It's a VB exe, not Access. Might be better ways to do this these days, this is how we created it way back so still use it as it works. On Finding Access, it looks in that order of "If" Statements so the first version of MS Access it finds it will open.


Private Sub Form_Load()
On Error GoTo ErrTrapAppActivate "Therapy Scheduling System" '** checks to see if the app is open already **

Form1.Hide
MsgBox "The Therapy Scheduling System is already open.", vbSystemModal
Unload Form1
Set Form1 = Nothing

End

CopyAndLoad:
If Dir("c:\PTS", vbDirectory) = "" Then MkDir ("c:\PTS") '** checks for the directory on PC, creates it if not there and copies the FE database to that location **

FileCopy "\\prog\apps\PTScheduling\PTScheduler.accdb", "c:\PTS\PTScheduler.accdb"

If Dir("C:\Program Files (x86)\Microsoft Office\OFFICE12\MSACCESS.EXE", vbDirectory) <> "" Then '** finds MS Access and opens the database **

Shell "C:\Program Files (x86)\Microsoft Office\OFFICE12\MSACCESS.EXE c:\PTS\PTScheduler.accdb", vbNormalFocus

Else

If Dir("C:\Program Files\Microsoft Office\OFFICE12\MSACCESS.EXE", vbDirectory) <> "" Then

Shell "C:\Program Files\Microsoft Office\OFFICE12\MSACCESS.EXE c:\PTS\PTScheduler.accdb", vbNormalFocus

Else

If Dir("C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE", vbDirectory) <> "" Then

Shell "C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE c:\PTS\PTScheduler.accdb", vbNormalFocus

Else

If Dir("C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE", vbDirectory) <> "" Then

Shell "C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE c:\PTS\PTScheduler.accdb", vbNormalFocus

Else

If Dir("E:\Program Files (x86)\Microsoft Office\Office12\msaccess.exe", vbDirectory) <> "" Then

Shell "E:\Program Files (x86)\Microsoft Office\Office12\msaccess.exe c:\PTS\PTScheduler.accdb", vbNormalFocus

Else

MsgBox "Could Not Find Microsoft Access Progrm. Please contact IS Programming Group.", vbSystemModal

End If

End If

End If

End If

End If
Unload Form1
Set Form1 = Nothing
End
Exit Sub
Resume

ErrTrap:

Select Case Err.Number

Case 5
GoTo CopyAndLoad
Case 70
MsgBox "Could Not Copy Current Version", vbSystemModal
Unload Form1
Set Form1 = Nothing
End

End Select

End Sub

[Remster]

Many thanks for that. Anyone else willing to share?

[isladogs]

Have a look at this lengthy thread https://www.accessforums.net/showthr...+newer+version
I would work through the thread for different methods. My approach is attached to posts #40 and #47

[Gicu]

Feel free to use my free utility http://forestbyte.com/ms-access-util...a-db-launcher/ that can distribute front-ends and also any additional files that might be needed locally by the users (such as Word mail-merge templates).

Cheers,

[Remster]

Thanks to everyone who's offered a suggestion.