Search results

post 45 shows the solution now to delete selected records.

https://www.access-programmers.co.uk/forums/threads/faking-a-multi-value-field.309635/ You can do this, but no matter how much I tried I could not think of a way to make this completely generic. So this will always require the user to do some coding. You will see that area in the example where...

@DakotaRidge, I read the requirement wrong. I assumed you wanted to clear certain fields, not certain records. So that solution will not help. If you are deleting records, let me do a new demo. Disregard that. If you add an "IsSensitive" field then this code should work sort of Public Function...

I post a lot of code as examples. It is not fully tested or error checked. You definitely want to test this thoroughly.

Stop wasting your time and simply get rid of all API calls. It is highly unlikely that you need them to do anything. They are likely just some window dressing, and if you are not an advanced programmer you will just waste time dealing with it.

The following code clears all fields in all tables in the datbase that are identified as sensitive in the description field. If the field is required it alerts you that it cannot clear it. Private Sub cmdDelSensitive_Click() Dim rtn As Long Me.txtOut = Null rtn = MsgBox("This will delete...

If I was going to do it for something this big, I would use the description field and mark all fields Now I would loop all tables create a recordset Identify the fields that are sensitive Delete using a delete query since I know the name and field. This would be very short. Did someone provide...

Unfortunately this takes some understanding of code. But you can get all the benefits of a MVF control and still normalize the data. https://www.access-programmers.co.uk/forums/threads/faking-a-multi-value-field.309635/

I am with @DakotaRidge because the above is completely misleading. You cannot simply replace an MVF with a combo. You cannot replace a MVF with a combobox. It requires - Child table - Subform - Combobox in the subform In regards to real estate a subform is going to take up way more space. So...

I think there are two big differences where MVFs are fine and where you most likely will get into problems down stream. I call it a "Simple List" or a "Complex List". You seem to be suggesting "simple lists" and thus not a big deal to go with MVF. But you really need to think about the...

This is a good point and you inherited this you may want to do it different. Somewhere in your code at the top of a module you have a module level constant, conOutDir It is not in this procedure as a procedure level constant. Since it is a constant that means it is hardwired to the application...

That means we need to see the rename code..

In addition to what has bee said, if I was trying to debug, my first step would be to add a debug.print to see if this loop is running away. Do Until .EOF varRet = SysCmd(acSysCmdUpdateMeter, intLoop) intLoop = intLoop + 1 debug.print intLoop ... .MoveNext...

Does this code break at a certain place? Personally, I would rewrite a lot of this thing. I would never be opening forms and reports in design view and then saving them. As far as I can tell there is no need to do this anyways. I am not sure why they do this. However, without knowing where...

If you use the code tags it is easier to read for everyone. I did some indenting Public Function CreatePDF(Optional strCalling As String) '************************************************************ 'Date Last Modified: 07/18/07 'Purpose: Loop through xtblRptInv for email custs and create PDFs...

@isladogs has a good explanation https://isladogs.co.uk/multivalued-fields/index.html Also this demo shows a lot of functions that can be used on a MVF. This demo uses three MVF to query three MVFs. At the top you can use the MVFs for Region, Work Category, and Work Type. This will filter...

Although lots of people avoid mvf for many reasons, the hidden table is properly normalized. It is either a junction table contraining the foreign key to the main table and a foreign key to a lookup table. Or it is a child table with the FK to the main table and the values.

Ahh, yes. The Rube Goldberg school of design. Always more fun. Why do simple when you can be complicated.

I think MS truly believes they are doing you a favor and making life easy. Goes along with allowing you to put spaces and characters in field names, every template using macros instead of vba, default properties and methods, and things like MVF. All things to make your life simpler in the short...

Something sounds very concerning. Unless you are building a commercial grade ERP I highly doubt this database is properly normalized with 450 tables. Correct me if I am wrong, but I really doubt it. Not trying to insult anyone here, but you are asking a somewhat trivial question but at the...