Search results

In another thread I was asking about issues with my reports opening minimized due tot he setaccesswindow code. I was able to get around that with some properties settings for the reports... However I just realized this morning that my export to excel no longer works. There are three modules...

Technically no... it does exactly what it is supposed to do. I just needed to tweak the properties of the reports to work the way I wanted them to along with the code. This does not happen anymore. After removing the code solutions I saw on the other sites the issue went away. It appears...

Colin... as usual I appreciate all of the help you give me. In this case it was something pretty stupid simple. I set the Auto Resize property to no on all of the reports and that fixed the problem.

It appears that it is related. I saw a few other posts on other sites regarding the exact same issue while using the showminimized coding. However no viable solution were available that I could find. I had thought that it was related to the borders and scrollbars but it was not as I tested...

Nothing to be sorry about... I always make backups and the overlap issue was easy to reverse. The issue with the reports is not related to the overlap thing. Could it be related to the SetAccessWindow (SW_SHOWMINIMIZED) in the code in the frm_loginform? Should I try to address the report thing...

Ok... I changed the option to overlapping instead of tabbed and that caused a whole new issue. On my frm_labtestinput I have 3 subforms and using the grow and shrink code discussed in another thread. When using overlapping rather than tabbed... when the subform displays on the frm_labtestinput...

I moved the calls from frm_home to frm_loginform and that seems to have solved it. My other question regarding the forced size on open remains though.

I cannot figure out why it randomly leaves the app window open in the background... sometimes it works... sometimes it doesn't. One more thing about this modification... I notice that if the end user has their access app maximized... the frm_home is also maximized instead of just the size of...

The frm_home is set to open at startup but has code in it to open the login form first then show the frm_home after that. I set the frm_home to be a popup and navigation pane is unchecked. This time it opened as a popup form but the application window is still up behind it (on the screen) and...

Colin, (or anyone else that is familiar with this) I am trying to use your code in teh SetAccessWindow database sample found here: https://www.access-programmers.co.uk/forums/showthread.php?t=293584 to only leave up my main form (frm_main). I do not need command buttons to make this happen... I...

Ahhh... I missed that... he used both. :banghead:

No... his has VBA7

Thanks Colin... everyone has access 2013 but just one user has it in 32 bit and all others including myself are on 64 bit versions. Trying it now.

I tried the Win64 as well remembering ridders mentioning that in another one of my posts but it didn't change anything. You are suggesting that I use the solution posted by arnelgp instead of what I am using??

I tried this but it errors on everything after the #Else stating it needed to be updated for 64 bit systems: #If VBA7 Then Private Declare PtrSafe Function SetWindowLong Lib "user32" _ Alias "SetWindowLongA" (ByVal hwnd As Long, _ ByVal nIndex As Long, ByVal dwNewLong As...

I have this module to hide the close buttons in the access application to force the user to use my command button on the main form to close the database. It has the PtrSafe added in to make it work with 64 bit systems but I have one user out of all users that is still on a 32 bit system. Is...

Mostly my fault. The thread started out in one direction and once some areas were figured out... I went deeper into other directions. Probably should have started new threads for the different issues.

Yea... when that happens... holding down the SHIFT key and clicking on the db will open it with no code running... then ALT+F11 will bring up the code window so the line can be commented out. I'm sure this isn't news to you though... you guys are great.

Gasman, If you comment out the HideAccessCloseButton on the second line of the code behind frm_home it will stop doing that to you when you open it. The mod_HideClose module should be the only one in the db that has ptrsafe code in it. If I knew what to put in... it can be made to work with both.

I tried this method next and this is pretty cool but alas... this has not sped up the loading time... well... it sped up the time it takes the database to load after logging in but it has lengthened the time it takes each form to open after that... 3 or 4 times longer than before. At the same...