backend on a FTP site.....
..thats a new one on me
I woudl expect that to the the worst of all worlds
not knowing what the application is (is it a local app, a web app, a newtworked app) its hard to say.
There's carious thigns you can do to improve performance in Access, although most of the need to improive perfromance coems when youhave more than 15..30 users or you are trying to run an Access front end talking to an Access back end on a remote server.
switching to a server back end PROVIDING YOUR APPLICATION IS DESIGNED FOR A SERVER is a smart call. that means doing as much of the processing / filtering on hte server and reduce the amount of data going up and down the network. designing for a server means retrieving only the data you actually need, it measn using unbound / disconnected recordsets, it menas playing to the strengths of the server. sadly it also means tht you loose most of the easy to use functionality of Access in form and report design
I'd rather be riding on the Tiger 800 or the Norton