You have not mentioned if the live viewer is going to be hosted on internet/web app or a fat client within your company If you talk about a Live update as and when the data reaches your server, I am not sure you can implement this just by using a database mechanism. You'll need a separate application/server app which will keep on publishing the data to the client after the client starts We are developing one such app but not exactly similar.
You have not mentioned if the live viewer is going to be hosted on internet/web app or a fat client within your company. If you talk about a Live update as and when the data reaches your server, I am not sure you can implement this just by using a database mechanism. You'll need a separate application/server app which will keep on publishing the data to the client after the client starts.
We are developing one such app but not exactly similar.
I would love to be able to view the data in a web app. Are you develping your app in house or with an outside vendor. Where can I find somone who can assist us with this?
Any ideas? – Michael Rosenberg Aug 8 at 19:13 Don't know if this response is any relevant as I'm writing this response after a month as I Haven't noticed your question. "We are developing this for a client of ours." – Muthu Sep 26 at 1:55.
If the Linux server is on your own LAN, you might be able to connect Access to it through ODBC. Depends on several things, not the least of which is suitable permissions in the dbms. In at least some versions of Access, use File | Get external data | Link Tables... In "Files of type", select "ODBC databases", and select a data source.
If you don't already have a DSN configured, you'll need to do that. (Control Panel, Administrative tools, Data sources. ).
Yes, the linux server is on our LAN, but as others are saying I don't want to over burden the server. I need to look into what the effect will be on the server and possibly adding a second server. – Michael Rosenberg Aug 8 at 19:33.
It is certainly possible. A direct link can be done with ODBC or with Java JDBC or with ActiveState Perl, DBI and DBI::Pg. I like Perl for reports so I would lean toward that.
Now, there may be reasons to not have direct access to the database for reporting. For one, reporting can cause a heavy load on the database when the database might have much better things to be doing with its time, like recording sales data. This depends on a lot on your specific situation including the type and frequency of reports and how much data volume your DB server is handling.In some cases you need to set up a second database server that is either fed with live data from the master or it gets a periodic (like daily) dump from the master.
This reporting server is then used to collect the data into nice groups for reports. This is sort of the situation you are in now. Before you change anything I recommend finding out if it was set up in that way intentionally.
Yes, I don't want to over burden the server. I wanted the reports real-time, but every hour would be fine too. I guess I can test this and see what kind of load it places on the server.
A second server is not out of the question. – Michael Rosenberg Aug 8 at 19:13.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.