Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

CPS doesn't point reports at the current database?!?

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

7 Posts

4 Users

0 Reactions

72 Views

RSS

ronmoses

(@ronmoses)

Posts: 158

Estimable Member

Topic starter

We have test, train, and dev environments in addition to our production environment. Each has its own database. I'm discovering that no custom chart reports will run in this environment because they're looking for the production database. Stock chart reports run fine, as do PM reports in the Reports module.

So what magic do I need to perform to make the application point the custom reports to the current database the way they do with the stock reports?

Posted : September 8, 2015 8:05 am

bruins1986

(@bruins1986)

Posts: 233

Reputable Member

CPS isn't something I am familiar with but I always had to change the database source to MLO_ which allowed the report to work in my Test and Live environments.

I wish I could give you the why or the how or the "what is that" but I just kind of stumbled upon that after I updated our Lab req and couldn't test it right (I looked at some older custom reports that worked). I'm not even sure if that is unique to us (our organization) or just CEMR.

Hopefully it will work for you otherwise sorry for any false hope seeing a response may have brung!

Mike

Posted : September 8, 2015 9:17 am

ronmoses

(@ronmoses)

Posts: 158

Estimable Member

Topic starter

I already tried creating an ODBC connection called MLO_ and saving it with that source, but it doesn't appear to help. It still looks for my production database (which is what the MLO_ connection is based on). There must be some property of the ODBC connection that I'm getting wrong, but I can't for the life of me guess what it could be.

Or, there's some way to change the database source in a Crystal Report to a "mystery source" and I'm not aware of it.

Posted : September 9, 2015 4:34 am

bruins1986

(@bruins1986)

Posts: 233

Reputable Member

I wish I could remember exactly what I had to do to connect and make it work right but it was a while ago... I tried to make the same edit and couldn't get it to work again, if I get some time I will try to figure it out again and let you know. Hopefully in the meantime someone else will post though.

Thanks

Mike

Posted : September 9, 2015 5:10 am

pandait

(@pandait)

Posts: 43

Trusted Member

Have you tried updating your datasource for the report to point to the new database?

In crystal reports go to Database > Set Datasource Location...

In the Set Datasource Location dialog that comes up there are two panes. The top pane is the Current Data Source: and the bottom is the Replace with:

Select the current datasource in the top pane and the datasource to your test database (or create a new one) in the bottom pane and click on the Update button. That will run the report against the database specified in the new connection. If the report contains other connections, for instance for subreports, you may have to scroll the top pane to see them and update those as well.

Posted : September 9, 2015 10:09 am

ronmoses

(@ronmoses)

Posts: 158

Estimable Member

Topic starter

Two problems with that idea:

1) I would need to maintain test, train, and dev versions of every custom report we have. That's well over 100 additional (redundant) reports to maintain.

2) Our train environment, while it has its own database, uses the same pool of Citrix servers as our production environment. So if I replace the reports on those servers with ones that point to the train database, they'll be rendered useless for production.

Posted : September 10, 2015 2:42 am

jamesedward

(@jamesedward)

Posts: 257

Reputable Member

On the EMR side, you would just need to login with the local/FAT-client into Network Training in order to reset the ODBC. Crystal uses whatever was the last connection as its basis. That way you wouldn't need to change the report structure.

When you want to go back to the full DB, just log back into that client. Assuming CPS/ODBC has somewhere else to connect to different DBs. There are some 'howevers', though if the report shows MASTERDIAGNOSIS table or SU_TUT as the db connector.

Posted : September 14, 2015 8:40 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0