Sharing Over the Internet

[toast]

Hello all,

I have a split Access 2010 database with plenty of VBA.

I've been reading up on my options for sharing this over the internet (cheaply and easily, without losing the VBA, and probably without the need for any concurrent users)... am I correct in surmising that the only sensible option is remote desktop, to either my computer or to an online host?

Thanks for any pointers.

 

[toast]

Thank you for your reply.

I'm sorry I missed the user group meeting; I've been away for a few days. I will certainly keep a look out for the next one.

Regarding my initial query, I am now wondering if I'd be better off migrating at this stage (before going live) to a better solution for sharing over the internet... the large stumbling block I predict with Remote Desktop is that we will need more than 1 concurrent user. Without server/multiple CALs this will obviously be a problem.

So I've been reading up on Office365 / Sharepoint (Access Services?) but I'll freely admit I'm more than a little confused... I've always been working over a simple LAN:

1. Are Office365 and Sharepoint (Access Services) the same thing?
2. Can you use an Access run-time frontend to connect to an Office365 backend? (most of the users don't have a copy of Access)
3. Can you disable browser access? (there is quite a bit of essential VBA)
4. Can you give restricted browser access so that some limited, web-compatible functions can be run?
5. Is it as simple as paying for an account on Office365, saving the tables to whatever format Office365 requires, uploading the backend to the server, then linking the frontend to the Office365 backend before distributing the frontend to the users?

My apologies for all the questions, but the more I'm reading on this the more confused I'm becoming!

 

[toast]

Thank you very much for the reply.

The questions possibly didn't make sense because of my confusion over what I was asking about!

To cut to the chase, I think sharepoint is probably not my solution at the moment; migration to SQL, run over the LAN with remote desktops as you suggest appears to be the best solution.

Concurrent remote users is almost impossible to predict at the moment. There are a number of satellite locations, but how frequently they need to use the database will depend upon how well they embrace the concept. Old dogs / new tricks / technophobes.