Search results

Thank you @CJ_London - Please see my response to the @theDBguy.

Thank you for the suggestion. I had been doing that, but with people working from home, etc.. every one has a diffent screen size.

For a datasheet - I want to know if the horizontal *vertical* scroll bar is present/visible (because there are too many row to display). This does not happen often in the app and when it does the users forget to look to the right side for the scroll bars. This means I get calls for help...

That works! Thank you for sharing - at least we now know what is going on even if we don't use the SplitForm approach.

Thank you for sharing this! I will check it out and get back to you!!

I did try one more thing - I showed the splitter bar and dragged down so the single form/row showed. If I changed the data there - the events in the class fire. If I do anything in the datasheet on the bottom, the events don't fire.

I agree - I will get this to them.

Based on the comments - I tried the class with same form, setting the Default View to Datasheet. All the events in the class work - which I didn't think it would! Colin( @isladogs ) I can solve the design issue in my app easily enough. I just need a form with a header and then a datasheet...

Everyone - thank you for the suggestions on split form alternatives! I use them to present dashboards to senior management. They like them because they feel more like excel to them, showing and hiding columns, moving columns etc. Colin(@isladogs) this is not for NW2 - its for a client. But...

1) Yep! If m_Form_Update you remove the comments and the MessageBox and then compile, Private Sub m_Form_AfterUpdate() will disappear. I just learned that! 2)Yes I expected the MsgBox "m_Form_AfterUpdate: " & m_Form.Name in clsForm events to display - it does display when it is a continuous...

Thanks Jack - you have confirmed what I found; the clsForm events are NOT firing for the Form_BeforeUpdate and Form_AfterUpdate on the split form. Those do fire when it is a continuous form.

I should have said in the original post the Class events for the Form are not firing See my comment to jdraw -

jdraw - I should have said in the original post that the events in the FORM fire - but the events in the CLASS module do not. My bad! Sorry for that. The events that are NOT firing for me are on the split form are in the CLASS Module: clsForm clsForm. m_Form_AfterUpdate...

I know the events fire because the message box appears. The clsForm events m_Form_AfterUpdate() and m_Form_BeforeUpdate are NOT firing in the split form. They do fire when the form is a continuous form.

The events are set The code does do that in the clsForm. The code is identical for each of the two forms. It works for the continuous form and the class events fire. It does not work for the split form.

I have attached a database which contains a sample the issue I have. I am implementing a clsForm so I don't have to paste the same code in over and over again. My class works perfectly when the form is a Standard form or Continuous form --> All events fire in the class!!! YEA (Thank you JOHN...

Thank You 561414! I am not sure I follow how I can "inspect" the fld variables - there is no intellisense after the ! - what should I have done? I did list all the properties - but often you have a property that is not valid/available for that type. How does a text field have decimal places?

Thank you DBGuy - your code does not get the decimal places. It did however give me an idea - check the fields properties. In my case, I need DecimalPlacesHold = fld.Properties("DecimalPlaces") A few items to note - some you may know but this is for others who may read this post the...

As part of my development process I create a table which holds all table names, field names, field type etc... I think of it as a data dictionary. I review this to confirm I have been consistent in naming conventions, field size, etc... I have everything working just fine with one exception...