adccommunitymod (AutomationDirect) asked a question.
Created Date: June 09,2015
Created By: botski
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Holy tearing out hair, Batman. I am using C More Version 6.1. I have an Event Manager database. I export it. I import it. The import works. Now I try to do something cool like add an event to the exported file. I select the last field from the export, copy it, and paste it into an empty line above the one that says "END OF RECORD (DO NOT MODIFY THIS ROW). I increment column A, change the data in columns B and C to be unique, and leave every other column untouched. Save. Now I go back to C More and try to import this new file and the import fails. The message is "Event with event number xyz - Unable to add to Event Manager Database ". (xyz is the number I had just incremented in column A) I am guessing that since Automation Direct decided to forgo the easy path of a CSV format in lieu of the mysterious and fragile Jet Database format, some sort of control character is getting whacked and Jet is all in tears. Perhaps Automation Direct could get an engineer to write the export/import functionality because most engineers know the concept of keeping things simple. CSV is your friend! Anyways, has anyone else found a way around this problem?
Created Date: June 09,2015
Created by: plcnut
I just tested with Cmore Ver6.12 and it worked fine.
I exported, Copied and pasted the last event (Leaving the same number of blank rows at the end), and then Saved and Closed Excel. The file imported without error, with the new event now showing up in my database.
I also prefer the good old fashioned CSV over the xls files...
Created Date: June 09,2015
Created by: botski
Thanks! Perhaps 6.12 fixed the problem. I'll grab it now to verify.
Created Date: June 09,2015
Created by: plcnut
Another thing: Each event is at least 2 rows long. I copied and pasted both rows to get an entire event. Are you sure your are copying the entire event?
Created Date: June 09,2015
Created by: botski
I am exporting as "Simple(Alarm) " which is only one line.
Created Date: June 09,2015
Created by: botski
Version 6.12 made no difference. Same error. If I export "All " rather than "Simple " I still have the same error. Perhaps my version of Excel is screwing with the file? I'll try Open Office, if it still exists. Grrrrrrrrr.
Created Date: June 09,2015
Created by: plcnut
FYI: When I open the file in Excel, it has 'Compatibility mode ' in parenthesis after the file name.
Created Date: June 09,2015
Created by: botski
At my company, engineers get stuff done (except for fighting this import problem) and database programmers stand around with coffee mugs and talk for hours about how that NULL character took weeks to find. :p
Created Date: June 10,2015
Created by: HMI Eng
Column C is the Tag Name. That error is a result of the Tag Name in Column C not existing in the Tag Name Database. You have to create the tag in the Tag Name Database and then import your the Event Manager.
Also, if you are inserting a row just above the bottom DO NOT MODIFY row, you are leaving blank rows. This will not work. You need to insert your new row just below the last event in the spreadsheet.
Created Date: June 09,2015
Created by: botski
Holy tearing out hair, Batman.
I am using C More Version 6.1. I have an Event Manager database. I export it. I import it. The import works.
Now I try to do something cool like add an event to the exported file. I select the last field from the export, copy it, and paste it into an empty line above the one that says "END OF RECORD (DO NOT MODIFY THIS ROW). I increment column A, change the data in columns B and C to be unique, and leave every other column untouched. Save.
Now I go back to C More and try to import this new file and the import fails. The message is "Event with event number xyz - Unable to add to Event Manager Database ". (xyz is the number I had just incremented in column A)
I am guessing that since Automation Direct decided to forgo the easy path of a CSV format in lieu of the mysterious and fragile Jet Database format, some sort of control character is getting whacked and Jet is all in tears. Perhaps Automation Direct could get an engineer to write the export/import functionality because most engineers know the concept of keeping things simple. CSV is your friend!
Anyways, has anyone else found a way around this problem?