Recent content by mjdemaris

Not necessarily. I have been using them quite extensively without the .Value property without any issues. Checking the values was the first thing I did, aside from pulling some hair out :(. However, I did discover that Access needed a Recompile :rolleyes: I suppose it had been too long since...

Hello all, I just deployed an update to our FE, and this code throws the error mentioned in the subject line: iFilter = TempVars!tv_SelectedUserDept Me.DS.Form.filter = "[DeptID] = " & iFilter Me.DS.Form.FilterOn = True It has been working fine for a long time. The value filtered...

Just happened to stumble on this thread while looking for the same answer... I created three long constants in a public module (Utilities), set values to RGB numbers: 100, 150, 200 for example. Then created a public function ColorTest as Long Public Function ColorTest() As Long ColorTest =...

Forgive me, but I don't understand how this code works, I think I'm missing something from this example.

So, what I'm seeing is that I must use ADO to create this table with a default value on a field?

I was considering this Doc, while writing this post. Going to try it in a minute.

DoCmd.RunSQL sSQL

The hidden form can be very useful if the OP needs to add functionality for updating the front end, forcing users to log out, etc. Using a custom 'Quit' button on a form can work with a hidden form as well. Pat was not stating that a user would need to force close the app, just providing a...

Hello everyone, Today's question: What is the correct syntax for creating a table with VBA, using an YesNo field, and setting it's default value to NO/0/False? sSQL = "CREATE TABLE TempSupercede (ItemID_FK INT, SupplierID_FK INT, PartNumber TEXT, DiscPart YesNo DEFAULT 0, Supercede YesNo...

I opened up the sample DB and commented out the ProperCase code and it still says it's dirty. I am not sure how it works for you if that's all you commented out. And by Dirty, I mean that if I debug.print dirty in the Before Update event, it says dirty is true. I guess the question becomes...

@Pat Hartman so, the form is not really dirty, then, after commenting out the proper case code on the exit event of the text box, as @theDBguy mentioned. Even without changing anything, the before update event fires. So, something is causing it to still think it's dirty. I've worked around...

Right, you will probably need to change the code to open the GEN_F_L1_SupplierDetail form, rather than #2 form. My apologies for not changing it ahead of time.

the DB is split, link to the three tables in the BE. There are two default value fields, however, defaults should only populate on a new record upon data entry, no? Also, I just realized one default value is probably not valid, for the payment method combo box. One last thing: I finished...

Except that event does not fire.

Riddle me this: I open a bound form, single table query, with ONE label whose caption is set on load event. The form is opened via a click event on a datasheet, filtered to the ID of the clicked record. The first text box gets the focus, also on load event. Without changing anything at all...