I have allready solved the problem... Never thought it would be that hard to read out the TOC with that many M$ API power to our disposal!
I had found a few libraries that could read the TOC of the CD in an instant using the ASPI drivers...

I'm using FreeDB now, however I wonder what these guys where thinking while developing their database and server capabilities. They are using a key of which they admit that it's almost unique. They generate this key of the offsets of the CD tracks... I could be wrong but isn't there a unique number on every CD, I have once written a procedure that could retrieve that code, but I never found any other use for it than determining which CD is in the drive, but I think that ID would be far more unique than using track-offsets!