Recent content by misscrf

Thank you for posting this solution. It's exactly what I needed, to use some listboxes for building criteria and appending that criteria onto a dynamic sql statement. Works like a charm!

This is such a great, elegant solution! Thanks for posting!

Thanks for the reply, Pat. The thing is, I don't want to alert the user. They don't need to be told to go back. Another issue is that the table field rules (required etc) can't throw errors, that are SQL errors. I would want to trap those and control that I just back out the record, instead...

Defintely!

I'm wondering if I should be making a SQL job instead, now that I'm thinking about it. That way, I can run it nightly, when people aren't using it, and the performance hit won't impact the end user.

Thank you for the response. Wouldn't the DELETE * FROM table WHERE NZ([field],0) = 0 need to loop to check all fields that are not the pk and fk? That's where I'm unsure of how to structure the routine. Also, what is the autoexec macro? Sorry, I don't really use macros, I write everything...

I have a normalized database (SQL) and Access for UI (forms/data entry). When I add a new sub-record, ie a form - subform record, it starts another record, and then there is an extra new record. It seems that if a user starts a new record, but then abandons it, a record is created in the table...

Thanks. I used to use timestamps. From what I have experienced, they are only really necessary, when you attempt to do things you shouldn't do. As long as you do things in the right order, they are superfluous.

nevermind. I moved it to after update and now it works. Thanks!

it is odbc sql linked tables. I don't have a timestamp. I'd rather not add one. I have lots of tables in this schema, and really don't want to add timestamp fields to all of them. I do want to be consistent. Is that needed?

I have form, where there is a combo that is first in line, to be set, on a new record. When that combo is changed (Change event), I want to check if we are on a new record. If we are, I want to save this record, and refresh some unbound textboxes, which are set on the form's Current code. To...

omg that was it. I had each textbox control set to their formulas, to start, so they did have a control source, which meant they weren't technically unbound text boxes. I cleared them out, and now it's good! Thank you!!!!!

I changed a couple of things around, including your suggestion and now the error says: run-time error '-2147352567 (80020009)': you can't assign a value to this object This is how I changed the code: Private Sub Form_Current() Dim Mytxt1 As String Dim Mytxt2 As String If...

I have the following onCurrent code, for a form, so I can set 2 unbound text boxes to create a dynamic string, for the user. The code checks if the form is on a new record. If so, it makes the 2 unbound text boxes be blank, so they don't show #Name errors. That is what you see, if none of the...

This is how I ended up solving the problem. It doesn't require any of the following: Hiding objects setting, resetting and unsetting listboxes every time the tab changes manage a please wait message This is my code, which only sets the listbox on the default tab, on load of the form. Then...