Search results

Update Query One common statement about MVF is that you cannot easily update them. However here again the update is exactly how you would do it in a traditional design. Like the other examples the hard part is understanding the hidden table. 1. The MVF Region field is a numeric storing the...

Union an MVF The question was asked here if you could union an MVF. https://www.access-programmers.co.uk/forums/threads/error-the-multi-valued-field-cannot-be-used-in-a-union-query.327050/ If by now you understand that an MVF if not a field but a display of a hidden table, then unioning an MVF...

You have a public variable myUser defined in two places. Defs and Defs_old. You cannot do that. Remove Defs_old

I am with plog, that make no sense. The only thing I can think you are trying to determine if that date already exists. If you are then there are easier way. if Dcount("*","qryWeeklyForecast", "LDOW = #" format (me.Ldow,"mm/dd/yyyy") & "#") > 0

From what I have seen, there is 1 and only one! You are looking at it. I have seen thousands of examples on this forum and other forums of inefficient designs. I have never thing anything even 1/100th of the purported scale of inefficiency. Everything else I have ever seen, you could help the...

I did not say there was not normalization problem I said it was not as much of a problem. 1. The OP probably does not have a lot of forms because the tables are not normalized, they have a lot of forms because they have multiple tables doing the same thing. Expense are expenses. Do not need and...

I find it funny that anyone would not want to use VBA over macros now a days. Since you do not have to write it yourself. I can ask chat to write pretty complicated things in vba and it comes out pretty complete. Maybe a little tweak if I did not ask the question well. It is faster for me to do...

Converting MVF to a Standard Junction / Child table. One concern about MVFs can be alleviated because if you ever want to convert it to a traditional junction table or child table, it is extremely simple to do. For example if you decide that you want to convert to SQL Server or another RDMS or...

If I provided assistance, I do not remember. However you can simplify the function a little. Public Function getParentForm(callingCtl As Access.Control) As Access.Form On Error GoTo errlbl Dim ctl As Object Set ctl = callingCtl.Parent Do While Not TypeOf ctl Is Access.Form Set ctl...

The before and after the collection is irrelevant. The inside and outside the loop is. Think of decorating Christmas Cookies, where you use a cookie cutter to cut out a christmas tree cookie and then decorate it. Think of this line Set dalsObj = New clsDalsTxtBox as creating a cookie with a...

Oh I see. You simply need one of the many available applications with the following 1. low code, no code application 2. supports unstructured data including free text 3. Allows development of graphics and speech based GUIs without code 4. Flexible to allow continuous additions 5. Design...

I see it now Private Sub Form_Load() Dim ctrl As Control Set mColRcControls = New Collection For Each ctrl In Me.Section(acDetail).Controls If ctrl.ControlType = acTextBox Then Set dalsObj = New clsDalsTxtBox dalsObj.fInit ctrl mColRcControls.Add dalsObj...

First look that looks correct. I will test in mine to see if I am not seeing something.

I am not sure if normalization is really the problem as much as consolidation if that is a term. For example you commonly see people build a table of Customers, Suppliers, etc.. Or a different table for different types of contacts. Sometimes these tables often have the same fields or nearly...

You kind of missed the point. The relationship diagram is invaluable if you use it to enforce referential integrity. It has very limited value if not. Then you have default joins but no way to enforce data integrity.

OMG! There is no teaching anybody anything. There is nothing for the user to do. You just set the rowsource of your different lists based on a query.

FYI, you do not have a relationship diagram, you have an image of default query joins. There is no referential integrity enforced on any of those relationships. So what's the point? This diagram only serves to set the default join type and all are inner joins.

Access has this cool thing called queries. You should give them a try. "Select * from tblSymptoms where condition = 'diabetes'" Provides a list of only diabetes symptoms to use as your rowsource. or "Select * from tblSymptoms where condition = 'dementia'"

If the references tables are not editable and you manage what goes in the lists, then the reference tables could stay in the front end but then you cannot enforce referential integrity. I then would then keep the source reference tables in the front end, but when the user gets a new front end it...

You can send email, snail mail, or use another file sharing app if you like.