Search results

Access works with relational databases. That is a very common technique for relational databases.

If they contained parentheses, that's good;) Column and object names should not include special characters or embedded spaces. Leave those things for labels.

Do you have Option Explicit at the top of every code module? Do you have the property set for the entire database so that it is automatically added to new modules?

Kinda' like what MS did to Access in 2007;)

What makes them alike? If they have attributes that make them similar, then you would use the attributes to link the items rather than doing it manually.

We don't use stones but we use furlongs to measure horse races and some industries use hundredweights.

If you want to retain history of who held what post, when - you have a many-many relationship. That requires three tables tblMember MemberID (autonumber PK) FirstName ...... tblPost PostID (autonumber PK) PostName ..... tblMemberPost MemberPostID (autonumber PK) MemberID (FK to tblMember)...

There shouldn't be any VBA that refers to the previous name. The BE is linked. So, if you change the name of the BE, you will get an error when you open the FE because the BE wasn't found. The linked tables manager can easily handle the relink and then the next time the database opens, it...

For a recordset to be updateable, EVERY part of the query must be updateable. Therefore you cannot create a query that sums a column of values and then use that sum to update a table because the "totals" part of the query is not updateable. I know, the database engine should be smart enough to...

Why would you leave If's dangling without end if's? Does the code even compile this way? Have you stepped through the code to see where it is running off the rails?

@Faoineag The people on the forum who are most likely to help you speak English. Your best option for help is to use Google Translate to translate your posts into English. It also helps if you mention that you are using a translator since sometimes technical terms get translated literally...

I've posted regarding that flaw on multiple occasions.

Given the way the left pushes abortion, you're lucky to have any grandchildren. Then there is the push to legalize drugs so that people can go through life in a stupor.

Notice how they carefully avoid the use of lawfare against the evil orange man. Wikipedia sucks. They've gone down the same dishonest road that 60 minutes travelled.

No, it is not properly normalized. You are experiencing that by the problems you are running into trying to use the data. I have interacted with SAP off and on at various clients for more than 40 years. Mostly I was building COBOL (originally) or Access (lately) applications to solve the...

Did it peak your interest sufficiently to look at one of your existing BE's and see if you had duplicate indexes for your FK's? If you didn't know already that Access automagically creates an index on each FK when you create a relationship, you may have lots of duplicates.

It is never too late to fix a design flaw like this. All you will be doing going forward is working around the way your data is stored. Therefore, the longer the issue goes unfixed, the less likely you are to ever fix it so the flaw becomes permanent until you get tired of working with the bad...

Me. refers to the current form or report object. When the code is running from a standard module or a standalone class module, no form or report is current until code execution returns to it. So, Me. is invalid outside of a form or report class module. Also, as Doc pointed out, VBA is an...

The value property of a combo refers to the BOUND value, NOT the visible string which comes from the RowSource query. It is also NEVER a partial string. It is ALWAYS a complete value when some item is selected. Me.RecordSource = "SELECT Name FROM TABLE_A WHERE ThePK = " & Me.cboName

Or, you could use the MSysObjects table in a query that uses the object type values that I posted.