[AccessD] Importing remote reports to client frontend

Doug Murphy dw-murphy at cox.net
Tue Sep 30 13:01:46 CDT 2014


Gustav,

Since there are no other takers, I'll offer an idea. You could have the
client app either download a text file from your server, import as report,
then delete the file. Or you could have the client app stream the file off
the server, save it to the client, import into a new report then delete the
temp text file. I did something like this long ago when the web tools
weren't that good, I'd stream a web page, which was a big table, into Access
then parse it to get the data I wanted. Not elegant, but it still works as
we have not changed that part of the application in 10 years.

Doug

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Monday, September 29, 2014 9:49 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Importing remote reports to client frontend

Hi all

A frontend A2013 application is distributed to clients.
It connects to tables and views at a remote SQL Server. No problem.

However, each client may have one or more reports with a custom layout.
These should be imported to the frontend.
This is quite easy if you have a local accdb containing the reports. But
would there be another method where you wouldn't need to distribute a local
accdb with the reports?

You could download a file, text or accdb, and import the reports from this,
but I would prefer a method where a local file is not needed. Any ideas?

/gustav
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list