Recent content by AC_Alberta

Thanks - I think I've got the desired effect I want by optical illusion.

Thanks. Not the effect I was trying to achieve so I'll stick with populating the subform using the sourceobject method to swap forms

Access terminology isn't my strong suite. They are subforms that you drag down from the design folder and plop into the main form. They are designated as 'child and whatever number' I leave it as it is and call it sub1 and then use sourceobject to put the form in.

Thanks Pat but both are popup and still getting the 438 error message. Beginning to think that arnelgp's post above maybe right and that it can't be done.

Hi, I'm after some help in getting the above to work.. Have no problem with parent forms fading in and out using the following: Public FF1, FF2, FF3 As Long FF1 = GetWindowLong(MyForm1.hWnd, GWL_EXSTYLE) FF1 = FF1 Or WS_EX_LAYERED SetWindowLong MyForm1.hWnd...

Still worked though. Well done. Oh, and commiserations for the rugby. We watch it over here in Canada and it's certainly getting traction in the schools as more and more teams are popping up.

Five stars to you. Went back and checked, it was 64. There was no 32 option to download but I tried it with x86. Works perfectly. You've saved me hour of angst and hair tearing. Many thanks indeed. I know where to come now for friendly advice.

Thanks, I'll give it a go and get back to you. Can't remember if the 32 or 64 options came up when I downloaded Runtime 2013 but will check.

Hi, I'm Andy from Alberta, came from the UK just over 17 years ago after retirement from Police and before that armed forces service. Self taught having started on Access 97 around 1998 constructing database programmes for specialist police departments. Still huge gaps in my knowledge though. As...

Hi, hope someone has the answer. When transferring a 2010 database from desktop to laptop which only has Runtime 2013, it usually opens without problems. However when I include fade in/out on open from autoexec macro, Runtime is throwing up the following error message: "There was an error in...