From a desktop Access 2010 application?

The database would be an Access 2010 ACCDB or SQL Server or MySQL
(most likely Access).

I am just trying to think of a way to synchronize availability between
the desktop and a website.

On another note, we just had someone put our 2010 application (as is)
using Amazon Web Services and it worked great (except for printing
reports, so far)! That was cool to see.

-paulw

On 25/05/2012 21:01, PW wrote:
Have you seen this?

http://dev.mysql.com/doc/refman/5.1/...-linked-tables

I've just done a similar thing with FMP on my Mac at home, and it works
brilliantly. Can't vouch for Access, but I can't see why it wouldn't
work well, too.

-Jen

The problem is, that's going to be really, really slow.

--
Danny Lesandrini
www.lesandrini.com/datafast/



"Jen P." wrote in message news:Oiu*ZZm8t (AT) news (DOT) chiark.greenend.org.uk...

On 25/05/2012 21:01, PW wrote:
Have you seen this?

http://dev.mysql.com/doc/refman/5.1/...-linked-tables

I've just done a similar thing with FMP on my Mac at home, and it works
brilliantly. Can't vouch for Access, but I can't see why it wouldn't
work well, too.

-Jen

On Mon, 28 May 2012 09:14:04 +0100, "Jen P." <jp337spork (AT) cam (DOT) ac.uk>
wrote:


I distribute an Access 2010 ACCDE ("executable") so I don't know how I
would do this.

Thanks!

-paulw

On 28/05/2012 13:10, Danny J. Lesandrini wrote:
Ahh... Well, I've never done it with Access, so no idea about it being
fast or slow. Pity. That could have been useful for something I'm
working on here, too! Might still give it a go, I guess, since it's a
relatively small DB that only a few people need access to...

Sorry, paulw, maybe someone else can give you a better answer (and I'm
not sure how it would work with a distributable file, either).

-Jen

On Fri, 25 May 2012 14:01:13 -0600, PW
<emailaddyinsig (AT) ifIremember (DOT) com> wrote:


These guys have figured it out:
http://www.fairsoftware.com/showorksweb.aspx

And yes, their application is an Access application (that will also
synch with an iPad).

If you optimize the application to only pull records required into forms,
then performance can be more then acceptable.

I been doing this setup for many years with some of my applications. I
distribute the FE to customers, but I host the data on SQL server that
running on one of my ISP's

While you can't place a mdb back end and use that over a WAN, using SQL
server as the back end dramatically changes things.

So well written applications that don't pull unnecessary records over the
internet work very well with a SQL server back end. I find that in some
cases the setup works as well or even better then a split FE/BE on a typical
office network if efforts are made to optimize the application for SQL
server.

I mention this idea of using SQL server as a possible solution in the
following article of mine:

http://www.kallal.ca//Wan/Wans.html


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal (AT) msn (DOT) com

On Wed, 6 Jun 2012 13:58:16 -0600, "Albert D. Kallal"
<PleaseNOSpamkallal (AT) msn (DOT) com> wrote:


Can't be an Access database Albert?

Is this what these guys are doing?

These guys have figured it out:
http://www.fairsoftware.com/showorksweb.aspx

-paul

Albert:

This is very true and is a good idea where it's planned for. I suppose each time I've tried it, I've simply used the
app as-is, without specifically engineering it for the latency.

--
Danny Lesandrini
www.lesandrini.com/datafast/



"Albert D. Kallal" wrote in message news:rDOzr.10535$gS5.2118 (AT) newsfe04 (DOT) iad...

If you optimize the application to only pull records required into forms,
then performance can be more then acceptable.

I been doing this setup for many years with some of my applications. I
distribute the FE to customers, but I host the data on SQL server that
running on one of my ISP's

While you can't place a mdb back end and use that over a WAN, using SQL
server as the back end dramatically changes things.

So well written applications that don't pull unnecessary records over the
internet work very well with a SQL server back end. I find that in some
cases the setup works as well or even better then a split FE/BE on a typical
office network if efforts are made to optimize the application for SQL
server.

I mention this idea of using SQL server as a possible solution in the
following article of mine:

http://www.kallal.ca//Wan/Wans.html


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal (AT) msn (DOT) com

Danny J. Lesandrini formulated the question :
I have also been linking Access front end databases (MDB/MDE) into
remote sql server databases (via the Internet) for years with good
success. My strategy has always been build the Access app in what I
refer to as "The Access Way", and then fix stuff where the performance
is not up to snuff. Much of the time I do ZERO speed up fixes.

When I discover a performance increase is necessary, I have found all I
need are some Passthrough queries running Stored Procs on the server
that reduce the number of records coming over the wire.

It is a rare occasion where I need to do something really heroic, like
unbound forms, temp tables, etc. to make it all work.

Rdub