Search results

Glad your figuring things out. I like to use Chr(39) etc. because it is easy to see as compared to "''" which can get a little tricky visually.

Take a look and you will see for each ComboBox the table that contains the drop down list is the row source. Your form has a table as the record source. This is how you will set up any additional forms and ComboBoxes. Good Luck.

Evan, what is the error message? Is Me.cboSystemType a text field? Try it on your other field Me.accSchoolName.

For the text field use Replace(Nz(Me.cboSystemType, ""), Chr(39), Chr(39) & Chr(39)) in place of Me.cboSystemType in your Dlookup. It will take care of the single quote issue.

Scott, you could save the primary key value of the current record in another table by placing the code in both the On Current (for other than Me.Newrecord) and in the After Insert form event (to capture new records). Docmd.RunSQL "UPDATE tblSaveKey SET tblSaveKey.SavedKey =" & Me!PrimaryKeyID...

You should be able to save each table to a local table. Right click on the table and you should see an option.

Would you like to attach your DB (if your able to) and I can better take a look. On the surface, it sounds like you are talking about ComboBox row sources and not the forms record source. If you included those tables in the forms record source that is not needed. The forms record source...

If your form is based on a query pulling fields from multiple tables then Access may not consider the recordsource updatable. There may be a field that is ambiguous (same name in multiple tables) making it not possible for Access to know which table is being updated.

You'll need to add the Cancel = 1 code which actually cancels the update. If MsgBox("The record has changed - do you want to save it?", _ vbYesNo + vbQuestion, "Save Changes") = vbNo Then Cancel = 1 Me.Undo End If

OK Duane, glad I could help. Good Luck with the rest of your project.

Thanks 'Rookie' for answering. I did not know what the data types where, just assumed ID was a number. If you are only concerned with the current date, then change the SQL to: SELECT tClients.ClientRef FROM tClients WHERE (((DCount("*","tContactEvents","ClientRef='" & [tClients].[ClientRef]...

Well, take a look at the link I provided. Using VBA you can easily add tables, fields etc. to BE databases and not worry about the actual data in the tables. You can do this with a separate update DB before the users begin using your new FE.

That's good to hear.

The reason I asked is if your not making any changes to the tables then you should only need to give your users your new front end and not worry about importing data. You just need to have the users relink to their BE location either with the Linked table manager or with VBA code you include.

You should be able to combine all the code for opening FormB and then FormC after FormB is open. Would you like to post your code?

Instead of creating a new environment, you can progamatically add tables, fields etc. to the backend DB's. What is motivating you to start over? Check out this link: http://aislebyaisle.com/access/vba_backend_code.htm

Not knowing how you set up your buttons but you can have the form open from the same On Click event: Docmd.OpenForm "FormB" Docmd.OpenForm "FormC"

Unfortunately you can't display a report in a form and vice versa. But, you can duplicate the report in a form (copy all the controls and recordsource) and just set the form Allow Deletes, Allow Edits to false and the RecordSet Type to Snapshot and it is just showing the information like you...

Phil, have you tried to set the default value for CU to [Forms]![NameOfYourMainForm]![NameOfComboBox] It would then automatically show that value on a new record. And as you said before, set the form to Data Entry.

The part about returning only clientRef where not Completed or not even attempted makes sense, but I was confused how the current date plays a part, maybe you could better explain. SELECT tClients.ClientRef FROM tClients WHERE (((DCount("*","tContactEvents","ClientRef=" &...