5: Invalid Procedure Call or argumentgreenspun.com : LUSENET : Anders Petersson's Freeware Forum : One Thread
I have tried running 3.1.15 and 3.1.16 and the problem exists for both.
Windows 2000 527 Catalogues The combined size of all the catalogues is 288 MB.
When I try to add another catalog, I get the following message:
Dialog Box Title = OCDB - Delete Damaged File?
This catalogue file seems to be corrupt or of an old catalogue standard (5: Invalid procedure call or argument). Do you want OCDB to delete it now? YES or NO
I have attempted to catalogue various CD's under the conditions listed above and have contuniually received the error message above. I have tried different CD's and different CD drives.
I would assume the number of CD's indexed is higher than normal and am concerned that I have ran into some problem with your software not being able to handle this size. I have not attempted to copy all the catalogues to a different computer to see if I get the same error there or not.
-- Anonymous, January 09, 2003
I haven't heard of this problem, but I'll try to dublicate it on my system. In the mean time: What happens if you move a dussin or so catalogues from the application path and try to make a new catalogue then?
-- Anonymous, January 13, 2003
Thanks for getting back to me on this. I have experimented. I moved 12 files out and attempted to "index" a new cd. Like always, it appeared the catalog was built, but when I attempted to open all the catalogs, I got the same "5:Invalid Procedure Call or argument" error. So, I removed 200 catalogues and finally removed all catalogs. Still got the same error. I uninstalled the OCDB software and re-installed version 3.1.15 and attempted to create a new CD catalogue in an empty catalogue and still got the same error. So, this seems to tell me this error has nothing to do with the number of catalogues I have. I have to wonder now if one of the program files is corrupt on my disk, although I would have thought that re- installing would have fixed any corrupt files. I ought to try 3.1.14 or whatever and see if that makes any difference.
Any suggestions? As you can tell, I have invested myself heavily in your program. I sure would like to get it working again.
-- Anonymous, January 21, 2003