> Hey Naresh, > after around 512 cycles in the loop all files in the dll stop opening. > Also the task manager doesn't show any kind of memory error or > violation. >
This sure sounds like the DLL isn't closing the file. I'm not up on the special resource restrictions that various MS OSes impose, but most OSes have a default size for how many simultaneous connections can be opened by each program. You can usually change this by reconfiguring the kernel. Anyway, 256 or 512 are pretty common values for this sort of configuration. I think it'd be worth your time to verify that the DLL really closes the file. And check the error handling to make sure that close is actually being called with the file refnum and isn't returning an error. Greg McKaskle
