Registering Custom Reports in Everest

[Tom]

Hello all,

Does anyone have any experience registering custom reports in Everest?

I have created a report in Crystal, copied into the Everest report
manager repository, created the parameter dialogue and registered it. I
can access the report from the reports menu and run it just fine from my
local desktop ( logging in as sup or my normal username ). But if I try
to login from different terminals, even as sup, I either a) do not see
the report at all, b) get an authentication failure or c) it opens the
parameter prompt full screen in the background and does nothing;
depending on what computer I run the application on.

thank you all in advance for any ideas

--
Thomas LaCicero
t...@myknobs.com
Office: 718.483.7912

[Crash]

You need to reset the reports menu:

1. File/setup/Preferences/Workstation Settings

2. Select the Interface tab

3. Click Reset Report Menus, then OK

4. Finally don't forget to save your menu settings by clicking the Everest logo in the top left corner of the main screen

[Tom]

Just tried that now and I get the same error, although that is good to
know because I would imagine that would have fixed the buggyness when I
first registered the report.

Still getting a error "Unable to connect: incorrect log on parameters."

It would seem to me the report is failing to connect to the DB. It
connects from my local machine I believe because I have a saved DB
connection. I would think I am just not using the correct connection or
login type for everest to use.

I am going to try and match the existing reports.

thank you for the response

> --
> You received this message because you are subscribed to the Google
> Groups "Everest (Icode/Versata) ERP Users Group" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/everest-erp/-/lUTZb9zpSy8J.
> To post to this group, send email to evere...@googlegroups.com.
> To unsubscribe from this group, send email to
> everest-erp...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/everest-erp?hl=en.

[Mike]

We had to go into SQL manager and screw around with permissions. In the end, Anyone that was using the client from a desktop had to be given explicit permission to the db to get the custom report to run. Strangely, we had no issues with users that were coming in through terminal services via RDP.

Sent from portable device. Please forgive typo's.

[Tom]

I changed the Data source type ( in crystal ) from SQL Native OLEDB to
Microsoft SQL OLEDB and it now seems to work.

Resetting the report menus did make the changes take affect immediately
though.

thank you again.

[Eddie]

Mike B,
What was the SQL permission you had to mess with?

[Michael Bender]

Tom,

I had to add the user's individual Windows domain account to the list of allowed SQL users via the SQL Admin account.  I probably could have done it via a group, but there was only one user that needed access to the specific report.  

The thing I never figured out was why users coming in to our client server to use the Everest client via Remote Desktop never had an issue.  It was only local users that were connecting via the Everest client on their desktop that had a problem.  And those permissions were only screwed up when they tried to run a custom report. 

Mike

  

On Mar 19, 2012, at 5:50 PM, Eddie wrote:

Mike B,
What was the SQL permission you had to mess with?

--
Email sent to Google Groups: "Everest (Icode/Versata) ERP Users Group" group.
 
- Post: evere...@googlegroups.com
- Unsubscribe: everest-erp...@googlegroups.com
- More options: http://groups.google.com/group/everest-erp?hl=en
-------------------
Access the Everest Resources Repository here: http://bit.ly/tbAy8L

[Eddie]

"The thing I never figured out was why users coming in to our client server to use the Everest client via Remote Desktop never had an issue.  It was only local users that were connecting via the Everest client on their desktop that had a problem.  And those permissions were only screwed up when they tried to run a custom report. "

Mike,

I can answer that surprisingly. The reason they were able to work remotely is because they are using the servers credentials as well as the servers components. Works the same way for terminals, which are nothing more then a video card, nic and plugs for keyboard and mouse. Basically a network capable KVM.

[Google Account]

Yeah, I get the hardware side.  I guess I was expecting the permissions model to be built on the Everest user credentials for everything accessed through the Everest interface, not everything except custom reports.  At any rate, it kind of works.

Mike

Sent from my iPad

--