Forum Discussion

rmnrdi's avatar
rmnrdi
Contributor
7 years ago

Multiple DDT CSV's one test

We have an application called Job Entry. It takes some of its data from the JobEntryData.csv as shown below.       var csvPath = "C:\\TestData\\JobEntryData.csv"; Driver = DDT.CSVDriver(c...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    My best guess is this...   You have too many CSV connections open.  You need to make sure that, when you're finished iterating through a CSV result set, you use DDT.CloseDriver to close the connection. There is a limitation in the database engine for CSV connections that restricts how many connections can be open.  

     

    I see, in your code, you have the call... but it's commented out.

     

    Change that line to DDT.CloseDriver(Driver.Name) and that should work.  You need to make sure you have the same sort of call for all your DDT drivers so that you're closing the connection when it's no longer needed

tristaanogre's avatar
tristaanogre
Esteemed Contributor

You are using the "Driver" variable in two different places... I'm assuming that's declared globally.  So, when you change the Driver to point to a different csv, that's replacing the Driver previously declared.  You should use a different variable for each driver.

rmnrdi's avatar
rmnrdi
Contributor
7 years ago

 

I don't know if this is going to work anyway.

 

For my various frame data csv's I may only have 4 rows, but in my main job entry csv I could have 50 rows.

 

What happens when I run out of rows on one csv, but I'm still indexing through the other?

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    You're not indexing through the second one anyways.... you're just grabbing the first row out of the FrameSource_Library.csv with no loop at all.  So, it really doesn't matter.  

     

    The key problem to your current code is reusing the "Driver" identifier for two different CSV files.  You should have a different identifier for each file so you can keep them distinct.  

    • rmnrdi's avatar
      rmnrdi
      Contributor
      7 years ago

      I know, but I need to index through them as well.

       

      I'm thinking the only way to do this is to create one giant csv with all possible fields and start my while loop with a function MapFields(Driver);

      Then every loop, it remaps all my variables to the next row in the document and I use the variables as need be based on logic from the program.

       

      I'd rather have something more modular, but it doesn't seem like I can do that without keeping multiple ddt drivers in sync.

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        7 years ago

        Here's the thing...  Let me demonstrate with sample code.

        function MyTest(){
    var Driver1 = DDT.CSVDriver('C:\\MyFolder\\MyFirstFile.csv')
    while (!Driver1.EOF()) {
         DoSomething()
         Driver1.Next()
    }
            DDT.CloseDriver(Driver1.Name);
}

functgion DoSomething(){
    var Driver2 = DDT.CSVDriver(C:\\MyFolder\\MySecondFile.csv')
    while (!Driver2.EOF()){
         DoSomethingElse()
         Driver2.Next()
    }
            DDT.CloseDriver(Driver2.Name)
}

        In the above sample, the number of lines in the two CSVs have no relation to each other.  For each record in Driver1, it will loop through all records in Driver2.  So, even if they have a different number of records, it doesn't matter.  

         

        From what I'm reading (and I may be wrong), this is what you're attempting to achieve.  You don't have to worry about the files being in sync, you just need to make sure that the drivers have unique identifiers.  That way, you'll always get all rows of both files.

         

        Now, if I'm misunderstanding how you're implementing your second driver, please clarify.  As it is, from what I see in your posted code, there is no direct relationship between the values in the first file and the values in the second file, just that you have two files.