Search results

With all respect, I'm advising, not doing your work for you. Advising is free. Doing work costs.

A screenshot is fine, but example is good, too. Just trying to get an idea of how it works. Not wasting anyone's time. On the board, anyway can take a look and advise.

Sorry for being so forensic in my questioning, just trying to get a clearer picture. So, each person is asked 25 questions, all of which can have the same answer? Or each person (of which there are 25) is asked one question and the answers are all recorded on one form? I'm also curious as to...

25 comboboxes on a form...? What are you capturing?

While you've seen my example, I don't know how helpful it can truly be as you've not answered my first question about your table structure?

Data Type mismatch? Sounds like a delimiter issue. What's the line you use to reference your combobox?

RecordSet objects don't like parameters unless they are defined via a QueryDef object first. If you search the form for 'Too Few Parameters: Expected' then you will find countless examples of this and how to solve it. Effectively the '[TempVars]![tmpFieldWorksID]' needs defined in the Query...

Completely aside, as I'm curious about the situation... What have you been doing there for the last thirteen years?

Er, there are no images. See this example for what I mean about table structure.

See what you mean, Brian. I wonder if I would personally do that or whether, as a manic data controller, I would envision a debit/credit system for points so as to always have a complete history/audit trail. (Me and bigger thinking. :D )

Go back to your table design, by the sounds of it. When I see Sun1, Sun2, Sun3, etc then it's indicative of a design flaw in your tables. Ditto the idea of having 34 queries. I have this horrible mental image of you having created some sort of matrix (days v classes) in an Excel style out of a...

How are you exporting the query: the TransferSpreadsheet method or by copying and pasting?

Any questions on how it actually works, let us know.

Re: delete a databese Why would you want to do this?

I would infer from the question 'lock' means to protect a database object (perhaps with password) from certain users. If this is the case I would suggest the thinking behind doing so is wrong, as it may infer the database is not form-driven, leaving users to happily use tables directly.

No, it can't be done in a table. Stop looking at the table and thinking it looks like Excel and so must to things like Excel. It's not Excel. If it acted like Excel, we would just use Excel and Access would be redundant. Access is a database. At table is for storing data. You can do...

The term for what namlian describes is import specification.

I'd add to be consistent with naming conventions. Why have some tables prefixed 'tbl' and not others? Prefix them all.

Not in a table. You do it in a query. Just create a new field in the query. Something like: Tally: [Points Earned] - [Points Used] Database design expects that you calculate values at run time rather than store values in a table.

More information required...or, at least, this is my understanding. You have a form you are using for data entry. The data entered obviously goes to an underlying table. On that data entry form you have a textbox where you enter a person's name and, on entering the next record you want to...