I like the Database Query Plugin, I find it very useful.  But it seems like every time I install it, my DVD Profiler starts opening up 3/4 page, then I have to stretch the sides back out to full screen, close DVD Profiler (via File/Exit), and it will open full screen next time just fine.  But if I leave it for awhile, then try to open up DVD Profiler again, it will open 3/4 page again (there will be a 3/4-screen white flash, then DVD Profiler opens 3/4 screen where the flash occurred).  Then it's the same routine all over again (stretch the sides back out to full screen, File/Exit).  If I uninstall the Database Query Plugin, everything is fine again, DVD Profiler opens full screen just like it's supposed to, each and every time.  It's a shame that it happens, I really like your Database Query Plugin, but I get really tired of streching DVD Profiler back out to full size once it's opened.  Maximizing it makes no difference, it still opens 3/4 page, randomly.

This on Windows XP SP3, all updates, + IE8, 17" standard size LCD monitor. 

I don't understand why the Database Query Plugin should make DVD Profiler open 3/4 page like that, I wish there was a way to fix that.      -kd5-

I did a Database Repair late yesterday, thinking that might resolve the issue but DVD Profiler still opened 3/4 page first time I opened it this morning.  Yeah, it's weird...

When it's going to open 3/4 page, there is always a 3/4-page-sized white flash that occurs just before DVD Profiler opens the same size.  DVD Profiler doesn't usually open exactly where the white flash occurred.  The white flash may occur in the middle of my screen, but DVD Profiler will usually open in the upper left corner of my monitor.  I can usually tell when DVD Profiler is going to open normally by the absence of that 3/4-page-sized white flash as it's opening.  It doesn't open like that all the time, but usually after it's not been opened for awhile.  If I uninstall the Database Query plugin, DVD Profiler goes back to opening full screen normally.  I'd much rather keep the plugin however, as I said before I really like it, it's very useful to me. 

I don't know if that helps but I thought that I would make sure you were aware of it.      -kd5-

Well, with a new release of the main app on the way, I'll probably be digging into this sooner rather than later.

Mark, I used to use on a DVD Profiler install on my old laptop and LOVE it.  I just installed the plugin on a new machine, though, and I'm getting this error in a dialogue box.  Thoughts or suggestions?

Quote:
Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.  The system cannot find the file specified

I can click the error away and the plugin shows up, but it pretty much stalls the program and I have to kill the whole thing and relaunch.

Edit to note:  I'm using the last full version, not the beta.

Thanks for the quick response.  I'm not in a particular hurry, but in the meantime is there something I can download to to get the plugin working?

Oh, and if I hadn't had this glitch with your plugin I wouldn't have learned about the update (I'm now on the beta) so thanks -- sincerely

Thanks again.  I have v1.0.x, v1.1.x, v2.0.50727, v3, v3.5 and v4.0.

Methinks I'll be patient.

Mark, I get a massive error when starting Database Query under the current 3.8.0 Beta. Please come back to me if you want more info.

Quoting Mark Harrison:

Quote:
Quoting TraunStaa:

Quote:
Mark, I get a massive error when starting Database Query under the current 3.8.0 Beta. Please come back to me if you want more info.

Yes, that isn't the least bit surprising.  I suspect most, if not all, plug-ins are probably broken with 3.8.  I should have a version compatible with 3.8 before its final release.

Actually Mark, so far, I have not found that to be true, with the exception of new fields not being supported. But then, I haven't tested every function, but those I have tested are still working as before (including bugs!).

Maybe the problem is something else. One thing I found was that some people were forgetting to copy the plugin folder over to the Beta installation folder. The plugin dll gets loaded, but other dependent code was not found and caused a crash. Could that be the case here?