Search results

Also, check the form's AllowAdditions, AllowDeletions, etc. on the properties Data tab(design view>>click on the form's upper, left-hand corner). Set them to "Yes" if any of the Allows... are set to No. That might be it.

That's that attitude I like to see. I'm glad you're having fun! I forgot. If you have a calculated textbox ([Units]*2) on your form, that might be causing problem you're having when you edit the data. I can't quite think of the solution right now(I've got a cramp), but maybe someone else can...

You could display your fields on a form in Datasheet View. Which will look much like an Excel spreadsheet. Assumming you've created a table that has the fields you want... 1.)Create a form and then add the fields from your table to the form's Recordsource property (View>>Properties on the menu...

I'm the only one Thanks for responding. I am the only person working on this db. This is the second time that this has happened. When the "Save As" dialog came up, I didn't save any of the changes and closed the form I was working w/, hoping that I could start from where I began w/ no changes...

Hello all, Can someone tell me why a "Save As" dialog occasionally appears when I'm closing a form that already has a valid name? Can I get past this because it causes many problems? I've been having this problem when editing forms. While making changes, if I try to close the form or save...

Does [criteria] refer to an actual field in your query? If not, you need to replace it w/ the actual name of that field you're searching on. ex. (... ,"[InvoiceID] =" & variable) The reason I'm confused is because [criteria] is also used by the function: (DAvg(expr, domain[, criteria])) and is...

Try... mo1 = DAvg("[Field]", "Query name", "[criteria] = " & variable2) You were close, but you didn't need the ' in the criteria. You may also need to add Str(variable2) to convert it to a string. You may have to try this a few times b/4 you get it right.

Almost... Using query builder on the report's RecordSource... add a field that should look just like: Barcode:"*z" & [ProductNumberField] & "*" But replace ProductNumberFiled w/ your field name. "Barcode" can be replaced w/ anything. It's basically a calculated field called "Barcode" using...

You could add a procedure in the form's OnCurrent Event that sets your combobox = to another field on your form. Do you have another field on your form that the comobox could be set to?

If multiples of any of the following fields exist in the query from different tables: ![Employee_Name] ![[Department] ![Start_Date] they will be deliniated by the table name. You must then include the table which they refer to in front of the field name. (i.e. [tblTableName.Employee_Name]...

can you add a field to your query I don't know if this helps, but... Maybe something is going wrong w/ the combobox value? I added a Barcode field to the query that my report is based on. Barcode:"*z" & [ProductNumberField] & "*" I added that as a Barcode field to my report. Hope that works.

Try... ="*z" & [Forms]![frmRcv]![Combo4] & "*" And if that doesn't work try converting the combo value into a string... ="*z" & str([Forms]![frmRcv]![Combo4]) & "*" HTH

If it works... Not to confuse things.... There's no sin in utilizing macros or wizards if needed. They provide the basics to getting your applications working the way you want. However, if you can accomplish the same task(which you can) by coding in VBA, then will be on your way to a more...

I may be way off the mark, but when you go to the table design view, select View>>Indexes on the menubar. You're saying that "Index1" exists in that list? If so, disregard this, but if not you may need to add it to this list. HTMS

Macros are basic, general, pre-defined Macros aren't special. They are just easy to use. Macros are pre-defined VBA functions that Microsoft added to assist users in automating their DBs if a developer has no experience using VBA. Macros include basic functions like opening forms, moving...

I finally figured this out And the winner.... This #Error would show up only on a few calculated controls(mainly when the user moved to an autonumber field). To alleviate the problem, I merely added an IIF() statement in the calculated control that tested the autonumber field for a null...

Are you using a form to display this information? If so, then what you may want is a combobox that is set up to display the description field("annual tune-up"), but its bound to the ID field("5"). 1.) Create a combobox 2.) Set its recordsource property = select ReqID field, "YourDescription"...

from one of the great Access Minds on this site (not me, of course). Try DoCmd.RunCommand acCmdSaveRecord This should save the record that you entered. I believe the command you have... docmd.save ...actually saves the form.

what type of recordset The index property is only available for certain types of recordsets. As chrismcbride suggested, check in help to find out which type of recordset supports the ".index". HTH

Thanks I'll tried setting the recordset = to the SQL and that did it. That works beautifully! Thanks for your input.