2 Replies Latest reply: May 15, 2014 9:55 AM by Bill Tilghman RSS

    Two Problems blinking JOIN and Excel Export

    Bill Tilghman

      The issue of the vanishing join surfaced this morning. A text file opened in Monarch v 7.02 with two joins. First join to a CSV file, second to an Access 2002 table.

      The DataPump extract came up with the wrong numbers and we looked at the model. 


      Opened the model and the Access join was NOT THERE!... closed the model.. looked around at other models, opened it back up and like magic it was BACK!  (?????? What tha???) Will check again tomorrow morning.  (Access DB was not open.)


      Second problem is not so surprising. Open 3 Excel databases and export 2 summaries each to 5 Access tables in one database.

      On the forth or fifth export into new tables one of two things happen... Either the database converts by magic to Access 97...(?) or it loses all of the table except the last one.

      I plan to remove Access 97 today...just thought of that... Since both live on the machine with DataPump. NExt step is to do a second export of the Excel data to fixed text and try to work another model to export to access. They want access for management to follow the numbers.

        • Two Problems blinking JOIN and Excel Export
          Grant Perkins



          I'm not entirely confident that this will prove to be the answer but ...


          Way back when beta testing V7 I had an incident where a model seemed to give very odd results extremely similar the the events you describe. Never found anything. A year or so ago someone else reported a very similar problem and I saw another instance. In both cases re-creating the model seemed to fix the problem. I think what had happened was that somehow the model file had become corrupt and the internal structure of its components was giving odd and unpredictable results. In fact I saw some very odd looking stuff when attempting to look into one of the problem files with an editor. I felt there was no way it could be recovered - or at least not recovered quicker than creating a new model.


          The other possibility might be that there is another slightly different version of the model file around and sometime you get that one instead. Especially possible if you are sometimes running the thing manually to check the process and sometimes using the automated version. But if you can discount that possibility then I would favour recreating the model in case the original has been corrupted my something.


          I'm not sure I can help with your second problem excpet to say I suppose it is possible that that also is due to some sort of file corruption, perhaps in the Project file if you are using Project Exports.


          Not sure if the Model and Project information option would make things visible - I don't relish the idea of try to corrupt a file to to find out!


          I hope this suggests something that might lead you to a solution.




          • Two Problems blinking JOIN and Excel Export
            Bill Tilghman

            Thanks for the help I'll rebuild it now.

            Another probelm that may need the same solution is the JOINS in two of my models keep dropping in the automation.  It ran for months and now it says the join does not exist (?)when I go in it is missing part of the path.  (?) Very strange, but rebuilding make a lot of sense.