[bmiller1@uhhg.org]

Our screens could be different because our claim reconciliation only allows date spans except for Medicare FSSINQ which includes name spans.

I did experience something similar with a very basic script that looped through a directory of 835s and entered each file name for eCare to import.  It took me a while to actually find what was causing it.  I noticed that sometimes if you tab through to hit a field that has default data that you need to change, sometimes eCare would not highlight the entire field.  I went through a lot of script iterations to try and work around it, but ultimately I asked our Nebo programmer to make that field blank by default.

In my experience, I would look for any time you're entering data to make sure it's 100% accurate and make sure the script is slow enough for eCare to react.  Sometimes it even throws an error with the SQL statement that is erroring and that could help.

 

[bmiller1@uhhg.org]

Sure does, thanks for the help!

[bmiller1@uhhg.org]

When he says connection he’s talking about what type of “Connect” command you’re using to connect to your application. Like, Connect “Application”, stRumba, stOCR, stStream, etc. Looks like you’re using the web connection though.

I was just having the same issue with an OCR popup box. Adding another Activate and Connect before the Pause command looking for the box fixed the issue.

For me it ended up looking like:

Activate “Pharmacy Clinical”, True
Connect “Pharmacy Clinical”, stOCR
Pause “&H39AD3F7A@79,46×81,69<1798449507"
Key “@@_{enter}”

[bmiller1@uhhg.org]

1. I updated the post with a screenshot of the error. At first I thought it was related to the OS because I had it on multiple dev boxes running XP, Win7 32 bit and 64 bit, but never experienced it on Server 2003 or Server 2008. Both Win7 dev boxes were built by me from scratch with a Windows disk. No images or ghosting used.

I did some Googling and tried a few things, but you can’t reproduce the error so it’s difficult to troubleshoot. It happens maybe once a month out of tens of thousands of transactions. This script posts payments, moves deductible/coins, adjusts contractuals, and changes other data, so it’s a fairly lengthy task for each record.

2. The filetime inside the .BDS matches the date modified under file properties. I didn’t know if there was a way to modify the .BDS filetime so that the mismatch didn’t matter, or fake it to make it match? The actual values match so I’m not sure what else to do.

No, these are .CSV files being opened as delimited files: D.Open_ F(“FileName”), ftDelimited, F(“Config”)

[bmiller1@uhhg.org]

I thought about that, but the file properties window only shows the date modified down to the minute.  The .BDS looks at it down to the second.  Any ideas on how to get the seconds?

I tried dir /t:w filename from command prompt, but that only gives minutes as well.

[bmiller1@uhhg.org]

I've never had to send a right click or double click via HLLAPI, sorry!

[Author]

Posts