Home Forums Discussions Problems usability issues with version 6.0.9

This is an awesome thread. Do I have permission to delete the post which contains an error message which can only mean something to a programmer?

at AmazingCharts.InteropFormLibrary.frmSendToPharmacy.(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4961 (win7RTMGDR.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
AmazingCharts.MainBusinessObjects
Assembly Version: 6.0.9.250
Win32 Version: 6.0.9.250
CodeBase: file:///C:/Program%20Files%20(x86)/Amazing%20Charts%206/AmazingCharts.MainBusinessObjects.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4957 (win7RTMGDR.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

No problem for me - I've collected my copies of that error from client machines, so nothing new there.

Know that AC is trying to find the fix.

Indy,

We know that AC is trying to find a fix. What we don't understand is why a version would be released with such issues with ePrescribe.

With each new version or beta, it seems to be an issue. Why do they test and retest and retest before they release a version when it comes to ePrescribe and TSP800?

No idea.

I'm fighting a WinServer install error on a remote machine, and I wonder why I can get detailed error logs to tail in the *nix world, and even paid tech support can't tell me why this thing bails 95% in.

The setupact.log stumps them too. If this server wasn't 2000 miles away I'd think about giving it a swift kick.

I don't understand. The software they are using should highlight the problem. Personally, I am not sure they understand how SQL impacts some of the workings of the program. But, if I am way off track, I will be happy to delete this post.

Last I talked to someone in support once I had isolated this in version 5.1.5 - it was an issue about registry entries that are made pertaining to the crystal reports stub they use that provides a path, and how that value gets changed - (even when the login in user is a non-admin user). It was on two Vista machines, that os a version of which "we should not speak".

I've never been a fan of registry entries - I much prefer config files, physical files - they are harder to bork.

Agreed. I think eMedware is a dinosaur which can be copied and pasted to a thumb drive then pasted to another computer and work fine.

I totally agree with you, Indy. Config, xml, and physical files are the way to go. I too, am not a fan of registry entries.

Bert, is your above post, with the exception handler from the prescription writer problem?

If so, the first line of that exception is where the problem resides. I don?t want to confuse folks here with my technical jargon. The people here are already frustrated enough with all this confusion. Unfortunately, even if that bug is fixed, it wouldn?t mean anything. It would have to be thoroughly tested, like you said, Bert. Who knows how long that would take? It?s not predictable.

That means someone from AC higher-ups will have to come to this user board, and explain this situation to the people. I?m not an AC developer, but I am a developer. I must say, this is a serious problem. It?s serious because people have paid their money. This should be a high-priority fix, not a beta. I?m sorry if I?m sounding a little hard. Sometimes I get a little passionate in times of needs.

Lawrence,

Go to the 3rd post to see the full error message. I can see putting out a release and finding bugs you never encountered. But, this has been an issue since 5.0.29 and above. It stems solely from Unmeaningful Use. Kinda hard to work on important stuff when the govt wants you to work on theirs.

Bert,

I did see stylnchris post (full error message) last month. Thanks for pointing me back to it. That error has to do with not finding a SQL connection, or a SQL connection String. I can understand the difficulties of getting a workable solution out to customers, but dealing with the government? Great point made.

There has to be a happy medium. On one hand you have to meet the government criteria, which must suck! Then on the other hand you have a loyal customer base that?s a little agitated with certain feature components. I can see AC being stuck between a rock and a hard place. This is where I can empathize and put myself in AC's shoes.

Exactly as I thought. Unfortunately, my SQL expert is willing to troubleshoot, but I am not having the issue.

Thanks Bert.

That is a lot to chew on, and right now, there are so many other pressing problems -- I have been lucky, maybe, with my "toast class" hardware. On the other hand, Medware (billing program) doesn't put anything like the strain of AC on the machinery, and this is all relatively new. The "crashes" I have experienced don't seem to be related to the hardware, however.

I see issues like slow-to-load imported items, slow E-Rx, etc., that don't really seem to be hardware problems, based on what I read on the forums.

I think (right now) that if I ever successfully transition completely to EMR, and especially if I really get any of that "incentive" money that I will think about hardware/server upgrades along the lines you recommend. For now, I'm just trying to get through the days!

And what do you suppose will come down the pike as a result of the "deal" that congress is working out with respect to the "debt limit"? I can only think that we may be returning to something like what I started with in 1975.

As for E-prescribe, I read somewhere that DEA is ok with scheduled drugs on eprescibe -- now it's up to SureScrips or whoever to put that into their code.

We use Medware. It is still one of the few programs left that doesn't require registry input. It uses .tps files for its database. You can copy and paste it to your flash drive, take it to Mexico, paste it to a computer there and use it.

I don't think AC should strain your computers. I personally think this is all SQL related.

We have been using eMedware since DOS days. It is the least troublesome thing about my practice.

Granted, security is not excellent, but when security becomes the main issue, much that is important gets lost. We don't really have a lot of people clamoring for that data -- and the ones who do care, don't have to steal it, they just get a subpoena.

And, it's easy to back up.

I have a Dell Laptop Intel i5 dual core Win 7 Pro and 4 GB ram. the return/enter key did not work in any fields of the progress notes in AC today. But Ctrl-enter works. Enter worked in all other programs. Then Microsoft came alone with an Automatic Update this evening. Viola, problem solved.

Hi Guys,

Just a line about the resolution of my pathetically slow computer with V6 Script Writer. Yes, that computer was getting loaded up & I had to replace it with a much faster Quad Processor. Things seem to be moving along fairly well now with writing Scripts.

Thanks & regards