Version 17 remainder statement error

Technical problems with Medisoft.
Post Reply
rstreetpt
Posts: 22
Joined: Thu Feb 17, 2011 5:35 pm

Version 17 remainder statement error

Post by rstreetpt » Thu Feb 17, 2011 5:55 pm

Hello,

Just upgraded from V12 to V17... I'm getting an error when going to print remainder statements in a batch. The error is

"qryPendingIns: Error 7200: AQE Error: State = 42000; NativeError = 2115; [iAnywhere Solutions][Advantage SQL Engine]Expected lexical element not found:) There was a problem parsing the WHERE clause in you SELECT statement. -- Location of error in the SQL statement is: 54(line: 2 column:34)"

I wasn't able to find any other posts...

User avatar
Gavin Walker
Posts: 4626
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Version 17 remainder statement error

Post by Gavin Walker » Thu Feb 17, 2011 6:38 pm

Try this. Go to File -> Program Options

Check Enforce Accept Assignment.

This is a bug in Medisoft.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

rstreetpt
Posts: 22
Joined: Thu Feb 17, 2011 5:35 pm

Re: Version 17 remainder statement error

Post by rstreetpt » Fri Feb 18, 2011 2:57 pm

I tried the Program options... didn't fix it, so I rebuilt indexes/packed data thinking that it was inconsistencies with my data... that didn't do it... so now I'm stuck.

User avatar
Gavin Walker
Posts: 4626
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Version 17 remainder statement error

Post by Gavin Walker » Mon Feb 21, 2011 10:10 am

Ok, look for a patient or guarantor with an apostrophe or some other invalid character in the Chart Number field. Use C:\Medisoft\Bin\MediUtils -> PowerTools utility to fix these. If you see an option "Only Show Bad Values" check that and then click Fix All. You can also use this utility to fix any bad insurance and procedure codes while you are at it.

rstreetpt
Posts: 22
Joined: Thu Feb 17, 2011 5:35 pm

Re: Version 17 remainder statement error

Post by rstreetpt » Thu Feb 24, 2011 1:16 pm

That fixed it...

THANKS!!!! :D

Post Reply