Search results

I have an append query that appends records from Table X to Table Y where Color is Null or <> "Red": WHERE (((tblColors.Color)<>"Red" Or (tblColors.Color) Is Null));This works fine. But when I try to add a third condition, like <> "Orange", it seems to ignore the <>Red and <>Orange criteria...

Got it! Used a slightly different approach: Dim x As Variant Dim strFirstArg As String Dim strSecondArg As String Dim strThirdArg As String If Len(Me.OpenArgs) > 0 Then 'Split creates a zero-based array from the input string x = Split(Me.OpenArgs, "|") strFirstArg = x(0)...

I have an open args statement with three values, separated by pipes ("|"). In the on load event of a form, I need to parse out the three values as strings. The following works if there are just two arg values. How can I change it so it works with three? Dim intPos As Integer Dim...

Any ideas?

I'm developing a database to manage survey data collected for a study. Individuals are seen for four visits and at each visit they complete a battery of surveys. Some surveys are repeated at each visit; some are new (but the survey schedule is predetermined). I'm going to store the survey...

Hmm ... then how would I model the fact that the employees and frontdesk people are children of businesses (i.e., one business can have many employees, and many frontdesk people), but freelancers don't have a parent? Maybe add to tblContacts a FK (BusinessID) to tblBusinesses, and include an...

For the call tracking, that is good model when you have only one entity (e.g., everyone called "contacts"). I have four. Also, the MS template doesn't normalize the telephone information. It hard codes each phone type into the contacts, which severely limits the database's flexibility when it...

I'm trying create a database to track contact information and calls (date, time, outcome) placed to: 1) businesses (e.g., calls to a main number), 2) business front desk people (e.g., a business may have 0, 1, or many front desk people) 3) business employees (calls to each employee), and 4)...

I would say I'm fairly knowledgeable regarding database development. I have probably built about 100 databases, most designed to handle data entry related to research studies, either directly in the field (i.e., using a laptop in real-time) or from data collected on paper forms (e.g...

Often database developers do not have control of the paper form. In my case, I am usually contracted to develop a data entry platform for a survey project already completed. The client has 1,000 completed surveys and they want to enter them in a reliable, quality-controlled environment. But...

The typical contact database would have most attributes hardcoded as field names: tblContacts ----------- ContactID FirstName LastName Age Gender NoChildren ContactYN etc. The "questionnaire" version would structure it this way: tblAttributes (~ to tblQuestions) ------------ AttributeID...

In my case, almost always a). But in both cases most Access experts recommend the similar, super-normalized (for lack of a better term) data model. To give you some ideas, I've attached two interesting approaches to improve the GUI of a questionnaire database. I got both from the Utter Access...

I'm inclined to agree. But in years of answering "how do I create a questionnaire database" posts, no one has come forth with a real example. Plenty of models, but no GUIs that can replicate the typical questionnaire that has different types of questions. Very true. No argument here. Moving...

I fully agree. Which is why I was surprised to see that Duane Hookom, in his popular At Your Survey database, used one Answer attribute: a text field called "Rspns" in tblResponses to store all types of answers (numeric, text, date, logical, etc.) He stores the data types and constraints for the...

Despite my appreciation for normalization, the typical 3-table structure has generally failed me when building questionnaire databases. It has failed for two reasons. First, the high degree of normalization severely limits the designer's ability to create a graphical user interface (GUI) that...

Well, this question gets at the issue a little differently. The normalizated structure for a typical questionnaire database has (at a minimum) these three tables: tblQuestions tblResponseOptions tblActualResponses Why is this structure not typically recommended for other types of databases...

I realize this post is a bit old so I'm not sure if anyone is still following it. But just in case ... DCrake: I'm curious why you didn't recommend a normalized structure for heather's survey database. For example: A normalized approach to this and similar questions would involve the...