7 replies to this topic

[David]

I am trying to import student information from a .csv file using the Import function in v9.03. I took an existing database and deleted the Category data and all of its sub-data. I have also inactivated most of the tutors (all but two). I imported Activity data with no problem. All of these actions preceded the import error.

When I tried to import the Student Information, I clicked on Import and got an "Error #31 Invalid subscript reference." I clicked Cancel on the resulting dialog and got an "Object OAPP is not found" message. I clicked Ignore and the program shut down.

Then I restarted the program, repaired the database and proceded to try another import. When I clicked on Import, I got a program error, "Invalid subscript reference." This time I clicked Ignore and the program started up the Text Import Wizard. All looked normal. I selected the .csv file I wanted to import and the target table, Student Information. I clicked Next. The proper screen came up and I selected the csv file type and left the field delimiter at Comma. The data looked great. I clicked the Next button. I got the column screen and dragged the column headers to the appropriate fields (I am sure I got them right as I have reproduced this error many times). I am only using the ID, First Name, Last Name, and Email fields.

I then clicked the Finish button and got the following message: "Function argument value, type, or count is invalid. Since I repeated the process several times, I can report that when I click Ignore in response to this message, I get the message again. When I click Cancel, the program shuts down.

On one previous attempt, the import utility actually imported a record consisting of a lone comma. In other words, I had one student record that was just a comma. On another occassion, it did not import anything, but it did not shut down.

The data looks good and there doesn't appear to be any unusual field lengths.

Any idea what's happening?

[Mon]

Perhaps there is a problem in the import file that you cannot see. The best way to check is to open the file with MS Excel and if it opens OK, to do a "Save As" from Excel and select "CSV". You can then use the saved file in AccuTrack for import. Try it and let us know if this helps.

[David]

Perhaps there is a problem in the import file that you cannot see.  The best way to check is to open the file with MS Excel and if it opens OK, to do a "Save As" from Excel and select "CSV".  You can then use the saved file in AccuTrack for import.  Try it and let us know if this helps.

<{POST_SNAPBACK}>

Mon,

I did that to produce the .csv file. The original Excel file looks fine and so does the .csv.

What next?

David

[cbasoz]

Hi David,
I think what you hit is an error that'd happen on rare circumstances and already fixed in internal built.
Would you test this:
Rename all files with a .dat extension to say .bkd and retry.
Please inform me of the result.

[David]

Hi David,
I think what you hit is an error that'd happen on rare circumstances and already fixed in internal built.
Would you test this:
Rename all files with a .dat extension to say .bkd and retry.
Please inform me of the result.

<{POST_SNAPBACK}>

Actually, I think I figured out what was happening. I went to a clean database and ran some tests. All went well until I changed the ID setting. The ID setting when I got the errors was "xxxxxxxxx" When I changed it to "XXXXXXXXX" the error stopped occuring. I was able to import with no problem.

This kind of makes sense to me for the "Function argument value, type, or count is invalid" message. However, I'm not sure it explains the "Invalid subscript reference" error.

I don't know if this is related to the the fix you wanted me to try, but it appears to have fixed my problem.

Does this explanation for the problem make sense to you guys? Is it possible it is valid?

David

[Mon]

This is funny, but another AccuTrack user reported the exact same error about an hour ago. I asked them to send their error log, and the error log showed that the problem occured when the Import Wizard tried to load their ID mask, which was set to "xxxxxxxxx". The correct format of the mask should be "XXXXXXXXX". When I tried the lower case mask on my system I got the same error message both of you reported. When I used the correct format (upper case) of the mask, the error disappeared.

This makes sense as the software does not recognize the 'x' as a valid formatting character for the mask ID. The mask ID is used in the Import screen to verify that the ID in the import file has the correct format. The ID format is loaded when the Import screen is launched, which was causing this error.

[David]

This is funny, but another AccuTrack user reported the exact same error about an hour ago.  I asked them to send their error log, and the error log showed that the problem occured when the Import Wizard tried to load their ID mask, which was set to "xxxxxxxxx".  The correct format of the mask should be "XXXXXXXXX".  When I tried the lower case mask on my system I got the same error message both of you reported.  When I used the correct format (upper case) of the mask, the error disappeared.

This makes sense as the software does not recognize the 'x' as a valid formatting character for the mask ID.  The mask ID is used in the Import screen to verify that the ID in the import file has the correct format.  The ID format is loaded when the Import screen is launched, which was causing this error.

<{POST_SNAPBACK}>

Thanks, Mon. I bet the reason two of us reported it on the same day is because the use of the lower case x in the mask seems to work just fine until the import occurs. We had no problems with the mask setting when we manually imported records or during normal operation of the software until the import. This suggests that maybe some error trapping within the software isn't working as it should. A minor error under most circumstances until a part of the program with more rigorous error trapping is launched.

By the way, the documentation shows the capital X in the table, but it doesn't contain anything that specifies that lower case is prohibited. Again, this is a small issue, but might help clarify the situation in the future, especially since the software allows the user to make the mistake. (And we will make them). :-)

Thanks for the quick feedback on all of this guys.

Happy Holidays to you, the rest of the staff, and your families.

David

[Mon]

You are right. We will try to trap this error in the ID Mask entry screen in future versions. Thanks. Happy holidays to you too.