X12 Parser

[Tony Grewal]

Hi Dave; any news on getting the C1COMMAND4 or C1COMMAND5 calls to work when it comes to parsing an 837EDI file -> XML via a call to the DLL. Currently there is no error when making the call but no file is output. Thanks.

************************* CONFIDENTIAL *******************************
Disclaimer - May 4, 2010

This email and any files transmitted with it are confidential and intended solely for the recipient. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions presented in this email are solely those of the author and might not represent those of Key Health Group or its affiliates. Warning: Although Key Health Group and its affiliates have taken reasonable precautions to ensure no viruses are present in this email, the company and its affiliates cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

[Com1 Software]

Tony,

We will see what we can do.

Thanks
Dave

[Com1 Software]

Tony,

We now have a fully functional DLL available that can talk to our demo
server.

Here is a link to it:
http://com1software.com/products/professional/f472.exe

In your c# code you will need to change this:

[DllImport("c:\\demof472\\demom471.dll")]

to this:

[DllImport("c:\\c1d0f472\\c1d0m471.dll")]


Regarding using the DLL with odbc here is an example of how to call
it.



using System.Runtime.InteropServices;
using System;

class PInvoke1App
{
[DllImport("c:\\c1d0f472\\c1d0m471.dll")]
static extern string C1COMMAND5(string strCaptiona, string
strCaptionb, string strCaptionc, string strCaptiond, string
strCaptionde, string strCaptiondf);

public static void Main()
{
string ret = C1COMMAND5("PARSE", "ODBC", "SOURCEFILE",
"DSN:TABLENAME",
"OW", "");
Console.WriteLine("Return Value: " + ret);
}

}


Let me know how it goes.

Thanks
Dave

[Tony Grewal]

Hi Dave; FYI: I just tried running the application from within .NET and
get the following message:

"This version of the model C1D0M471 is no longer the most current
version of this product. To download and try the latest versions of the
Model C1D0M471 go to http://www.com1software.com"

Disclaimer - May 7, 2010
This email and any files transmitted with it are confidential and intended solely for com1-software-...@googlegroups.com. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Key Health Group. Warning: Although Key Health Group has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

[Com1 Software]

Tony,

I just tested it and it seems ok.

Make sure you have downloaded the latest version form here.

http://com1software.com/products/professional/f472.exe


Thanks
Dave

[Tony Grewal]

Hi Dave; I just ran your X12 DLL parser successfully. However I would
like to manipulate the CI837.XML file to allow for up to 56 line items.
I have created the export file and it is ready to go. Where do I place
the file for this to occur successfully? Thanks.

-----Original Message-----
From: com1-software-...@googlegroups.com
[mailto:com1-software-...@googlegroups.com] On Behalf Of
Com1 Software
Sent: Tuesday, May 11, 2010 1:32 PM
To: Com1 Software DLL Development
Subject: Re: X12 Parser

Disclaimer - May 11, 2010

[Tony Grewal]

Dave; just a quick follow up to the last email. The new C1837P.XML file
which can allow for up to 100 line items which I created a few days ago
is located in the folder where the executable files lay e.g.
C:\C1D0F472. But the output XML file only shows up to 10 line items.
Thanks.

-----Original Message-----
From: com1-software-...@googlegroups.com
[mailto:com1-software-...@googlegroups.com] On Behalf Of
Com1 Software
Sent: Tuesday, May 11, 2010 1:32 PM
To: Com1 Software DLL Development
Subject: Re: X12 Parser

Disclaimer - May 11, 2010

[Tony Grewal]

Hi Dave; does the command below with regard to the ODBC source work even
though no destination table(s) name is/are provided? I am being curious
since it failed to work with me. Thanks.

-----Original Message-----
From: com1-software-...@googlegroups.com
[mailto:com1-software-...@googlegroups.com] On Behalf Of
Com1 Software
Sent: Friday, May 07, 2010 12:36 PM
To: Com1 Software DLL Development
Subject: Re: X12 Parser

[Com1 Software]

Tony,

When it defaults back to 10 like that it sounds like it is not
detecting c1837p.xml map.

The c1837p.xml map may need to be in the same folder as the dll or it
may
need to be in your application exe. folder.

I will look to see if we can add some information about what map was
used
to the parse.log.

Thanks
Dave

[Com1 Software]

Tony,

In your destination for odbc you have to have the dsn and the table
name present.
If the table is not present in your sql database then the program will
build it. Also the dsn and table name
are separated by a colon.

The odbc is different from the other conversion in this issue.

You also have to have your dsn set up correctly as well as have an
odbc driver that we can properly write to.
Here is a link to some discussion we had on it.
http://forums.fivetechsupport.com/viewtopic.php?f=3&t=15369&p=81301&hilit=odbc+odbc+key#p81301

FYI we have a bug on the 837 odbc if you are trying to convert a
directory. The
fix for that problem will be in the next release.

Also in the odbc we have a limit of 255 fields.

Hope that helps.

Thanks
Dave

[Tony Grewal]

Hi Dave; my CI837P.XML file is in the folder where my program references the DLL. It makes no difference to the outcome. Perhaps when you 'built' the DLL, it was set to read only 10 claim items at the time. Thanks for looking into this. This is an urgent matter for us in the meantime. I will test the ODBC side of things as well.

[Tony Grewal]

Simply does not work. I have created a System DSN, pointed it to a new database called X12; no tables exist there currently. I have tested the connection. It is fine. The entities are separated by a colon as in your example. However the program still 'blows up'. Would sending you the file in question be of some help to you? Thanks.

[Com1 Software]

Tony,

Does the odbc work with the c1d0f252 parser on that machine?

Thanks
Dave

On May 12, 1:52 pm, "Tony Grewal" <tgre...@keyhealth.net> wrote:
> Simply does not work. I have created a System DSN, pointed it to a new database called X12; no tables exist there currently. I have tested the connection. It is fine. The entities are separated by a colon as in your example. However the program still 'blows up'. Would sending you the file in question be of some help to you? Thanks.
>
> -----Original Message-----
> From: com1-software-...@googlegroups.com [mailto:com1-software-...@googlegroups.com] On Behalf Of Com1 Software
> Sent: Wednesday, May 12, 2010 9:29 AM
> To: Com1 Software DLL Development
> Subject: Re: X12 Parser
>
> Tony,
>
> In your destination for odbc you have to have the dsn and the table
> name present.
> If the table is not present in your sql database then the program will
> build it. Also the dsn and table name
> are separated by a colon.
>
> The odbc is different from the other conversion in this issue.
>
> You also have to have your dsn set up correctly as well as have an
> odbc driver that we can properly write to.

> Here is a link to some discussion we had on it.http://forums.fivetechsupport.com/viewtopic.php?f=3&t=15369&p=81301&h...

[Tony Grewal]

No; it makes no difference. It complains that there is already a column by a name in the table etc...

[Com1 Software]

I have seen that error if the map has a part of a tag missing like the
top
<CONFIGURATION>

What database are you using MS SQL 2008, 2005, ect?

[Tony Grewal]

I am attempting to write to a SQL Server 2005 database.

[Tony Grewal]

Also; when attempting to download and install the latest version of C1D0F472, one gets an error message before installation that states that parameter PARM1 does not exist.

Error description: Error BASE/1003 Variable does not exist: PARM1

I did not install the latest version.

[Tony Grewal]

Dave; the link to your X12 Parser DLL trial version appears to be broken this morning (m471).

[infor...@com1software.com]

Tony,

I fixed the page:

Here is the link

http://com1software.com/products/professional/f472.exe

Thanks
Dave

[Com1 Software]

Tony

If you are still having problems you may want to try ms sql 2008
express
There may be issues with 2005 and the odbc driver.

Let me know

Thanks
Dave

[Tony Grewal]

Well I ran SQL Profiler and this is what I got:

Msg 2705, Level 16, State 3, Line 1
Column names in each table must be unique. Column name 'MODA8' in table 'Test123' is specified more than once.

Your script to create the tables appears to be trying to create the column MODA8 up to 3 times.

I will send U a more detailed breakdown in a few minutes.

[infor...@com1software.com]

Tony,

If it is not a mapping issue (you don't have dups) and you have your tags correct

I would test and see if it works with ms sql 2008
http://www.microsoft.com/express/database/

If you want to send your map file to me directly I would be glad to look at it

Thanks
Dave

[Kevin Kingsbury]

How can I be removed from this group? The unsubscribe function isn't working. I no longer am dealing with any transaction projects.

[Tony Grewal]

Hi Dave; so I corrected the script and created a table called Test123 and was successful in inserting the data into the table. There is unfortunately still a problem when it comes to inserting more than 10 line items even after the C1837P.XML file has been edited to include more than 10 line items. I created the extra columns in the table and re-ran the application but notice that these fields still remain blank i.e. NULL. Any ideas?

[infor...@com1software.com]

Tony,

I will run some tests on how the dll loads the map file and I will let you know

Thanks
Dave

[Tony Grewal]

Thanks Dave. What is interesting however is that if I run the application to produce XML output from an EDI file (with the new C1837P.XML file in the same project folder), I successfully get the extra line items output. So one would expect the operation to the database to make use of this mapping file and output the extra items.

-----Original Message-----
From: com1-software-...@googlegroups.com [mailto:com1-software-...@googlegroups.com] On Behalf Of infor...@com1software.com
Sent: Thursday, May 13, 2010 4:02 PM
To: com1-software-...@googlegroups.com
Subject: RE: X12 Parser

[infor...@com1software.com]

Tony,

That is very helpful information, it sounds like we may not be loading the
map in the odbc.

Last week over on the x12 parser group Mike found a pretty good one when he found
we had a problem with converting a directory in odbc.
http://groups.google.com/group/x12-parser/browse_thread/thread/63b1401497c76c76

Are you doing this all on ms2005 sql?

[Tony Grewal]

Glad to help. Please let me know when you feel you have a fix. It looks like we're close.

[Tony Grewal]

Yes; we're on SQL 2005 for the project I'm on but will be migrating to 2008 soon. We do use 2008 in other areas of the company's business.

[infor...@com1software.com]

No, we just use it to test with.

We use dbf files since most of our critical apps use smaller
databases. We like the dbf because we can have
many index keys per table.

A lot of the people I work with use ADO, however I have only used it once many years ago.

I find the dbf files are able to take on a lot more data than I have ever expected.

The nice thing we have if we ever need it, is a thing we call RDD Replacable Database
Drivers, I can replace the native dbf that harbour uses with something other database like an
sql.

Good to hear that it is working on the 2005

[Tony Grewal]

Hello Dave; have you had any luck with the map in the ODBC element? Thanks.

[Com1 Software]

Tony,

I have added a map log to the parse log.

That should help us figure what is happening with your mapping fields.

Let me know how it goes.

Thanks
Dave

[Tony Grewal]

Thanks Dave; I will try a little later this afternoon.

[Tony Grewal]

Hi Dave; so I downloaded the latest version of the DLL i.e. C1D0M471.DLL and was successful in parsing the EDI file and producing an XML plus inserting of the data into a SQL 2005 database. However I still have the problem of not being able to insert more than 10 line items into the test table even though I have created the extra columns and have the CI837XML 'mapping' file in the same directory. How can I use the map log to the parse file to help me? Thanks.

[Tony Grewal]

Hi Dave; I also notice that when I run my .NET application and use the DLL to parse my EDI file -> XML, the application repeatedly informs me that the current version of the model C1D0M471 is not the most current version even though I have downloaded the latest version from your site. I just tried downloading it again but get a 404 error.

[infor...@com1software.com]

Tony,

The map log is merged into the parse.log file at the end.

It should say default map or what file and directory it got the map from.


Thanks
Dave

[Com1 Software]

Tony,

As far as the latest version download:

Here is the link, it looks ok now.
http://com1software.com/products/professional/f472.exe

This link is no longer available.
http://com1software.com/products/professional/m471.exe

If you are downloading from the Parser DLL Page
http://com1software.com/c1051.htm

You may need to refresh the page in your browser, since we did change
the link.

Not sure what to think regarding latest version warning, it sounds
like
you might have the dll placed in more that one location and may be
calling
an older version.

Thanks
Dave

[Com1 Software]

Tony,

In the latest version we have map log data in the parse.log, what does
it say when you see the failure?

Here is what you might see in the log

Map Log Data.
05/17/10 14:29:11 - Loading Configuration
XML 837 Map File Present
Map File : C1837I.XML
Current Directory =C1D0F252
Field Count 25


Thanks
Dave

[Tony Grewal]

Hi Dave; I just downloaded your latest version of the X12 parser. The DLL exists only in the one place; in the created folder on my hard drive; namely in this case: C:\C1D0F472.

I reference c1d0m471.dll in my C# code in .NET programmatically and see that it has a date of 5/17/2010 3:18 PM. It does not exist anywhere else on my machine.

I make 2 calls to the C1COMMAND5 command in my code; one to parse an 837EDI file to produce an XML output file. The other to parse the same 837EDI file and inserts the data into a SQL Server 2005 database. The calls are shown below.

The first call:

string refx = C1COMMAND5("PARSE", "XML", strFiles[i], @"C:\\Documents and Settings\\bgrewal\\My Documents\\EDI\\EDI files\\X12\\" + strFiles[i].Substring(intpos + 1, strFiles[i].Length - intpos - 1), "OW", "");

The second call:

string ret = C1COMMAND5("PARSE", "ODBC", strFiles[i], "X12:Test123", "", "");

Now here's the rub:

When I run the application as a stand alone (not calling it programmatically) but by double clicking the icon on my desktop, here are the steps that I take:

I create and place a new C1837P.XML mapping file (in the C1D0F472 folder) because I am expecting more than 10 line items in the resulting XML file. In this case I create up to 99 mapping nodes. When I run the application by double clicking the C1D0F472 icon, it creates a parse.log file in the folder and parses the 837EDI file correctly and I get all my data in XML format. It works very well. I have attached the log file for your perusal.

Now here's the anomaly. When I call the DLL from C# code in .NET, it does NOT produce a parse.log file. The output consists of only 10 line items even though the mapping file is present in the C1D0F472 folder. Therefore the 2 ways of running the application produce 2 different results.

Plus the call informing me that the current version is out of date still appears twice only when called from code. Once after the 837EDI is parsed to produce the XML file and secondly after the data has been inserted into the database.

I hope this explanation of what is going on helps you. I would love to see this application do what it does programmatically as it does as a manually run application. We would to move on quickly and make a decision soon as to whether to purchase your product or not. Please let me know if you need anymore information or if I am doing something wrong. Thanks.

[Tony Grewal]

Also when I run the application from the command line, I get the same result: successful insertion into the database but only 10 line items showing.

[Com1 Software]

Tony,


Here is an application I wrote to test with

using System.Runtime.InteropServices;
using System;


class PInvoke1App
{
[DllImport("c:\\c1d0f472\\c1d0m471.dll")]
static extern string C1COMMAND5(string strCaptiona, string
strCaptionb, string strCaptionc, string strCaptiond, string
strCaptionde, string strCaptiondf);

public static void Main()
{

string ret = C1COMMAND5("PARSE", "XML", "test.837", "", "OW",

"");
Console.WriteLine("Return Value: " + ret);
}
}

Once I compiled it I copied it over to a folder called c:\test, copied
over
my c1837i.xml with only two fields mapped, to see if we are loading
the map
properly.

Ran it and it ran fine.

I ran it with odbc and it worked as well

I looked at your parse log that you attached and I see the map logs
loading and it looks like you have a lot of fields like
you would expect.

I did notice that your test file was multi ST as well.


FYI in the Overview tab the parser is being called just like in the
exe, In the Parser Functions tab you have the
Call the DLL using this example button that allows you to test the dll
calling it in a c++ environment.

I will be doing some more tests and will let you know.

Thanks
Dave

> ...
>
> read more »
>
>  parse.log
> 4KViewDownload

[Tony Grewal]

Nope; no good. I still get the following message after it has parsed and created the XML file:

This version of the Model C1D0M471 is no longer the
most current version of this product.
To download and try the latest version of the Model C1D0M471
go to http://www.com1software.com.

Using:
string ret = C1COMMAND5("PARSE", "ODBC", strFiles[i], "X12:Test123", "OW", "");

to send the data to the database with the "OW" switch as shown does not remove the records from the table. Therefore the data appears twice.

Perhaps you can look to see under what circumstances the message above appears and where it is written in your code. It is obviously being called by something. Try locating where that is. Thanks Dave.

Disclaimer - May 18, 2010

[Tony Grewal]

If I run the parser from the Parser Functions tab, I get the correct result in the XML file depending upon the mapping file placed in the C:\C1D0F472 folder. One still gets the message that the application is out of date. Try running this using the file attached. If you try to run the ODBC part (with the extra fields added in the table in the database), you do not get the fields above 10 being populated. Weird.

If you run it from the Overview tab by clicking the 'Parse X12' button, the result again differs depending on the mapping file.

None of this seems to matter if one calls the DLL programmatically in NET; you get 10 line items no matter what and the error message comes up.

Disclaimer - May 18, 2010

[Tony Grewal]

Dave; please tell me why the latest downloaded application of the X12 Parser keeps telling me that it is out of date once it has finished parsing a file? Have you run it yourself? Do you see it?

Disclaimer - May 18, 2010

[Com1 Software]

Tony,

We made an improvement in the demo DLL interface that may correct the
problem.
How long was the job running?

Thanks
Dave

> ...
>
> read more »

[Com1 Software]

Tony,

I will be doing some more testing from the #c, it is weird on the 10
line issue.

One thought I wanted to remind you of regarding the odbc, is we have a
255 barrier.

http://groups.google.com/group/x12-parser/browse_thread/thread/cd9e71da087abc02#


Thanks
Dave

> ...
>
> read more »
>
>  Key_Mesa_040210
> 49KViewDownload

[Tony Grewal]

The new version still throws up the same message that the DLL is not up to date plus now it breaks when I make the call to ODBC to insert the data into the DB. I have included the error log file your program outputs.

Disclaimer - May 20, 2010

[Tony Grewal]

Dave; we are really interested in your application. However there are some issues which we would love to see addressed as soon as possible. As stated before, if I run the 472 application as a stand alone from my desktop and parse the 837EDI -> XML with the C1837P.XML mapping file, the correct output is produced. However if I send the data to the database, only 10 line items are inserted. So the application looks at the mapping file when parsing to produce an XML file but fails to 'recognize' it when attempting the ODBC part.

Programmatically (from within .NET and C#), the output only contains 10 line items for both the XML and database output. Also the application raises a warning message that a newer version exists.

Your latest version of the X12 Parser 'breaks' when used programmatically from within .NET principally when attempting to write to the database. I sent you a copy of the error file earlier.

Thanks.

P.S. Would it be possible to obtain the source code if we buy the application?

Disclaimer - May 20, 2010

[Com1 Software]

Tony,

What kind of c# application are you creating?

I have been testing using console applications.

The new version thing is very odd. It very well could be tied to
your mapping issue.

I am seeing a problem with the odbc in the parser dll, it looks like
a problem with it getting the destination correctly. We saw a similar
problem with
parsing a directory of files that we were able to correct.


Thanks
Dave

> ...
>
> read more »
>
>  X12ErrorLog.txt
> 18KViewDownload

[Tony Grewal]

I am calling your application's DLL as shown in the attachment.

I call or invoke the PInvokeApp method by calling it from the main body of code. I 'import' in the DLL and define the arguments passed to it as shown.

Hi Dave; here is an explanation of how we call your DLL from C# in .NET.

Basically, if you follow the code, 837EDI files in a directory are processed one at a time in 2 steps. The first step is to parse it to produce an XML file. Then the same file is parsed again but this time the data is stored (via ODBC) in a SQL Server database.

In the case of the database, I took the script that creates the Test123 table and added additional columns to accommodate more than 10 line items per claim. The code for that is shown in the 2nd part of the X12.txt attachment.

The first call in the code to produce the XML output runs without any problem until it is finished. Your DLL pops an alert box up to inform the user that the code is old and that one should download the latest version. One has to click the 'OK' button to remove the message alert box. Having done this, the second part runs which inserts the data into the database. At then end the popup appears again. So your complied DLL is looking at the version of the DLL and thinks it's out of date.

For the latter, no more than 10 line items are inserted per claim in the Table. I have placed a modified C1837P.XML mapping file in the folder where the DLL sits but this seems to make no difference. So the DLL simply appears to ignore it.

If I run the X12 application as a stand alone from my desktop (C:\C1D0F252) and have the mapping file in that folder, there is no problem. The program runs without a popup and displays the extra line items. I have attached the mapping file (C1837P.XML) plus the XML output from the non C# called version (Test.XML).

So there you have it. I hope this makes sense. I really would like to get this working properly. Thanks for looking into this.

Disclaimer - May 21, 2010