I meant that he just quit working on it. He wrote that himself, that he was going to do other things and would no longer respond to any communication regarding Access. He left the website up, but as far as I know, it has remained a completely static site. And he left no docs on where he got the info on how to do his magic. I wrote him a few times back when he was still active, and he always quickly helped me fix whatever I was having trouble with, but he absolutely refused to ever answer any questions about his own sources.
In any case, the APICopyMemory call was wrong - I had that last parameter as Long, instead of LongPtr. However, correcting it did not fix the problem - the app still bombs when that call is made. No error; Access just shuts down. I suspect that maybe there are some other preparatory calls to other routines that have this same mistake, but I have no idea how to find them. Is there some way to determine which parameters and function returns must be converted to LongPtr, and which ones remain Long? Could I just make ALL of them LongPtr? I tried that, but it still bombs, so I don't know if maybe I fixed what needed to be fixed, but also broke something that should not have been changed, or if there is something else altogether that is making this happen.
You mention conversion utilities. I know of such things from the old .mdb format to .accdb, but I don't need that - this has been in .accdb format since 2007 first came out. There are things that convert to SQL Server and various non-Access forms, but again, that doesn't apply here. Could you maybe point me to something specific, or at least, exactly what sort of 'conversion utility' I should be searching for?
