Search results

A very stupid, lazy way to automate it in Access 2003, kinda using VBA:- The DB1.mde line is optional (will just use the database name). Steve

I really like it. I will have a play with it and try to substitute this into one of my forms in my networked, multi-user database that has been running now for 4 years using the temporary tables approach. p.s. Couldn't you have in the Private Sub Form_Unload so that it transacts Deletes too...

I went with DAO as well originally but it is slow over a network so I converted all my long-running DAO stuff to SQL for speed because the customer wasn't too happy with the speed of saving big orders (with lots of sub-items) and when running a convert-to-invoice procedure and batch printing at...

Hi hk1, I managed to implement a solution that has been working for some time in a small golf business in Surrey with 10 users. I am using temporary tables to present a copy of the data and then the changes are written out using a SQL statement if the users saves at the end. Step1 (for the...

Do I have to create a "quote" form for each of the other data entry forms such as Customer Details, Payments, Stock, Suppliers, Bills, etc., yes I see your thinking, make all the changes in a staging form of some kind, like a separate, temporary table, and then convert, or update, to the real...

BeforeUpdate with subforms is a problem because the main form record is saved as you move to the subform.

Would love to know what these simpler strategies are.

I don't understand this comment - please rephrase. Please let me in on them! For speed - one database I am supporting has over a million records. The WHERE clause speeds up the SELECT INTO (make table) statement.

Yes, I know. That's why it turns out you can make A Case for Temporary Tables in Data Entry as suggested by Thales750. In an environment that uses a form/subform interface where you need to cancel changes to the entire record/subrecord and to prevent gaps in your order number sequence, this is...

OK, the good news is that the escape key worked for the main form but bad news is it didn't seem to work on the subform. Once I move to another "record" in the subform it appears to have saved the data on the preceding subform record. Is there a way that I can undo the entire record change?

OK Thanks, I'll try that.....

Thanks gemma-the-husky and Simon_MT, that's locking sorted. Can I ask you about rolling back forms and subforms, I am really struggling with bound forms when it comes to cancelling changes.

When an Access form is bound to the actual recordset you are exposing the user to real data....argh, and a lock on that record. If a user changes the data in that form or a subform the record is automatically saved, yikes. The best thing about going with unbound forms (i.e. bound to temp...

You are spot on, GalaxiomAtHome - no doubt you've pondered these issues in the past. I use a counter in the table which is read when the form is opened and which is incremented on save so that if the user attempts to save changes on that record and the counters don't match then the user gets...

I feel very strongly about this topic as it has plagued every database I have written in Access and after Thales750's comments I am pleased to see I am not the only one who thinks the way Access automatically saves records when using bound forms is against the general consensus of Office...

Regarding the use on the server problem, I seem to remember that "True" should be changed to "-1" (and similarly "False" to "0") when using checkboxes in SQL, but other than that they should work. Might be worth a try though. To set the text box on the form with a database value you either...

Ok, I have tried calling Form_AfterUpdate or UpdateTotals directly from the Form_Delete event, which fires when a user deletes a record, and the routines DO actually fire, but they fire too early. I need something that fires automatically AFTER the delete record. Anyway, after several hours of...

On my form I have an AfterUpdate event that updates some grand totals, but it doesn't fire when a record is DELETED. I have tried putting the UpdateTotals code in the Form_Delete event, but it runs too early (i.e. before the actual delete) so the values are still the original ones, and thus...