![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I would appreciate any comment. I want MS Access to act as a reporting tool accessing Oracle tables. The Oracle database is populated by another database application, but this application cannot create the report I want in this situation. I can easily develop the application I need to create the report and I'd like to deploy this tool as a published application over Citrix so users can simply fireup Access, run the report and print. I have no experience with setting up Runtime/ multiuser environments with Access; so my ignorant question is if the database is just throwing out a report from linked tables over ODBC (with a few simply queries in the background) do I have to deal with settting up the runtime application or can access handle that on it's own? |
#3
| |||
| |||
|
|
"lukethegooner" <lukethegooner (AT) gmail (DOT) com> wrote in message news:e1a1d34a-3145-4985-9c56-392fd7d2142f (AT) s19g2000prg (DOT) googlegroups.com... I would appreciate any comment. I want MS Access to act as a reporting tool accessing Oracle tables. The Oracle database is populated by another database application, but this application cannot create the report I want in this situation. I can easily develop the application I need to create the report and I'd like to deploy this tool as a published application over Citrix so users can simply fireup Access, run the report and print. I have no experience with setting up Runtime/ multiuser environments with Access; so my ignorant question is if the database is just throwing out a report from linked tables over ODBC (with a few simply queries in the background) do I have to deal with settting up the runtime application or can access handle that on it's own? The runtime IS Access (the exact same executable) so your question doesn't make much sense. The advantage of using the runtime with Citrix is that your users wouldn't have to own a valid license for Access. If they already have that then the runtime provides no additional value. |
#4
| |||
| |||
|
|
The runtime IS Access (the exact same executable) so your question doesn'tmake much sense. *The advantage of using the runtime with Citrix is that yourusers wouldn't have to own a valid license for Access. *If they already have that then the runtime provides no additional value. |
#5
| |||
| |||
|
|
On 23 Jan, 00:29, "Rick Brandt" <rickbran... (AT) hotmail (DOT) com> wrote: The runtime IS Access (the exact same executable) so your question doesn't make much sense. *The advantage of using the runtime with Citrix is that your users wouldn't have to own a valid license for Access. *If they already have that then the runtime provides no additional value. OOOOOOOOOOOOOk, Thanks for the comments so far, gretly appreciated ... as you can guess I'm not much of a blackbelt in deplying Access ... So my question from those replies is ... So if I were to install Access on the production Citrix server(s), link it to the Oracle tables, setup the queries and reports as required, make an application then publish it to 10 users it would work fine? Luke |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
Thanks for the comments so far, gretly appreciated ... as you can guess I'm not much of a blackbelt in deplying Access ... So my question from those replies is ... So if I were to install Access on the production Citrix server(s), link it to the Oracle tables, setup the queries and reports as required, make an application then publish it to 10 users it would work fine? Sure, but to be legal all users would also have to have Access installed on the PC that they use to connect to the Citrix server (or at least hold a license for it). |
![]() |
| Thread Tools | |
| Display Modes | |
| |