Hi Alex,

It's interesting though (to me at least) that older laptops that I've seen can 'scroll' the Windows desktop. I've seen laptops with a 'base' resolution of 800x600 display a 1024x768 window by allowing moving the mouse beyond the edge, causing the hidden part to be visible.
I has thought this was a OS 'service' but I guess it's a hardware service.

cheers

>>Alex,
>>
>>>Looks like vfp ignores the message from the operating system regarding it's window being constrained by the size of the desktop.
>>
>>I don't think it's working like you think.
>>
>>I think Access is doing the equivalent of a sysmetric(1)/(2) call and Access itself is keeping you from making the window too big. As you can see the O/S doesn't care how big a window is.
>
>Hi David,
>
>I did some digging in newsgroups-land while I was trying to do this (make a window larger than the desktop), and didn't come accross the technical answer again until now that I searched again to reply to you (sorry for the delay). Here's what I had found as the reason why windows (the OS) prevents applications from growing beyond the size (not the boundaries) of the desktop:
>
>----Begining of newsgroups quote:
>>Can somebody tell me why the following code doesn't produce a 1000 x 1000
>>pixels window (see the parameters in function CreateWindow(...)), but a 800
>>x 600 window (this is the size of my desktop)?
>
>I feel tempted to point out the obvious sillieness of creating a window
>larger than the screen. Ah well. What you will need to do is handle the
>WM_WINDOWPOSCHANGING message. This is typically handled by DefWindowProc
>that sends a WM_GETMINMAXINFO message that retrieves the largest and
>smallest dimensions an overlapped window can be. Handle it yourslef to
>prevent it clipping the windwo size to the desktop size.
>
>-----End of newsgroups quote.
>
>I don't think that vfp or the api offers an easy way to intercept the above messages. This is probably yet another thing that vfp does its own [and unstandard] way.
>
>Thanks for trying though!
>
>Alex