I have been wandering through Google all day, getting lots of data but not much information!
I have been developing what was originally seen as a single user Access db for a small charity. However, these things tend to expand as users become more aware of what might be possible, so it's turned into quite a complex system to which at least 3 users would like access (with a small 'a').
They don't have much money!!! They are trying to limit admin costs so that the max of what they raise can be spent on the work of the charity. There was even some balking at buying ONE licence for Office 2007, but we are over that now.
Here is my current plan. What I want to know is (a) are there any obvious technical snags, and (b), more importantly, are there any licensing issues with what I propose.
Current plan:
The part time administrator for the charity has a copy of the database on her own PC.
We can buy a copy of LogMeIn Pro which will allow remote access to her PC, and enable remote printing of reports etc, remote updates to the db.
We organise it so that the admin person has chunks of time when she can use the db, and other chunks of time are allocated to each of the other two users for exclusive access using LogMeIn.(Thus, there is never to be more than one person using the Office 2007 s/w at the same time ... I am hoping this gets round licensing issues with having only one licence??? ... and also ensures there are no concurrency issues to address)
In fact, I have a preference for only the administrator being able to do updates to the db (for 'human reasons' rather than technical). If the other users have only 'read only' access, and the ability to run reports, does this mitigate any licensing problems? (I imagine it makes not a blind bit of difference, but worth asking.)
Possible future plan:
Users are getting all excited about putting the db on a server with remote access for several people. I have told them (I hope correctly) that in that case each user will need a licence for Office 2007, (expensive) in addition to a fee for whoever hosts the db for us. I also don't currently have the expertise to set this up (tho' I dare say I can acquire it). Can anyone confirm that if I split the db, and the tables go on a server, and each user has a 'front end' all users will need a full licence? I assume the front ends can't work via the Access Run Time thingy?
Oh my! Little hobby programmer that I am, I didn't really know what I was letting myself in for, did I?
I have been developing what was originally seen as a single user Access db for a small charity. However, these things tend to expand as users become more aware of what might be possible, so it's turned into quite a complex system to which at least 3 users would like access (with a small 'a').
They don't have much money!!! They are trying to limit admin costs so that the max of what they raise can be spent on the work of the charity. There was even some balking at buying ONE licence for Office 2007, but we are over that now.
Here is my current plan. What I want to know is (a) are there any obvious technical snags, and (b), more importantly, are there any licensing issues with what I propose.
Current plan:
The part time administrator for the charity has a copy of the database on her own PC.
We can buy a copy of LogMeIn Pro which will allow remote access to her PC, and enable remote printing of reports etc, remote updates to the db.
We organise it so that the admin person has chunks of time when she can use the db, and other chunks of time are allocated to each of the other two users for exclusive access using LogMeIn.(Thus, there is never to be more than one person using the Office 2007 s/w at the same time ... I am hoping this gets round licensing issues with having only one licence??? ... and also ensures there are no concurrency issues to address)
In fact, I have a preference for only the administrator being able to do updates to the db (for 'human reasons' rather than technical). If the other users have only 'read only' access, and the ability to run reports, does this mitigate any licensing problems? (I imagine it makes not a blind bit of difference, but worth asking.)
Possible future plan:
Users are getting all excited about putting the db on a server with remote access for several people. I have told them (I hope correctly) that in that case each user will need a licence for Office 2007, (expensive) in addition to a fee for whoever hosts the db for us. I also don't currently have the expertise to set this up (tho' I dare say I can acquire it). Can anyone confirm that if I split the db, and the tables go on a server, and each user has a 'front end' all users will need a full licence? I assume the front ends can't work via the Access Run Time thingy?
Oh my! Little hobby programmer that I am, I didn't really know what I was letting myself in for, did I?
Comment