Search results

I believe your source has misunderstood. The order by applied to the whole, not "the last member-query of the set of queries in the union". UNION precedes ORDER BY in order of execution, so the ORDER BY is applied to the already unioned data. A subquery is not necessary.

Thus trading an underscore for a heap of extra typing that distracts from the actual code.

Yes but the same principle applies. A MySQL database engine is required to read the files. I assumed the links in posts 3 & 4 covered that back in 2021. Pat raised a related discussion. The BTW parts of threads can be quite interesting.

As it is with any Windows file. The extension is just a convenient way to associate the file with a program. For example, MS Word files don't need the docx extension to be able to be opened by Word. Information about the nature of files (other than simple text files) is stored in the first line...

The backup file extensions are bak. The actual database files are mdf with the log are ldf. The bak file contains the data plus some of the logs, depending on the type of backup used. The default location of the mdf, ldf and bak files can be configured. The tables and other objects don't live...

That "append" is exactly the clumsy process that the technique in my sample database avoids entirely. However Pat's suggestion is a solution frequently used by many developers. Unfortunately 561414 has totally derailed the thread with their obsession of trying to justify their extremely...

I realise this is an old post but Pat's contribution most clearly demonstrates a misunderstanding about databases. (I expect Pat actually knows better but her explanation as it was written is wrong and will be misleading the database newcomers.) Microsoft SQL Server Management Studio (MSSMS)...

I said it was similar. I didn't say it was exactly what they needed. If you read the context of the original thread you would realise the sample database was provided only to demonstrate how to add records to a table without having to prepopulate the table with empty records. Relying on...

Have a look at this sample database. It has a novel form structure that is remarkably close to what you are trying to build. It shows how to prepopulate virtual records on a continuous subform with the records only becoming real when a value is entered. It is remarkably simple with very little...

Absolutely do not do this. A design like that is not extensible without redesigning the tables and forms. Bad bad bad.

You would do it with a form for the date and FacilityID plus any other common factors relating to the assessment. Then a subform for the criteria. BTW Does a facility always have all of the ninety criteria? Will there potentially be more criteria added in the future? Are the scores for the...

SetId is text so you need to concatenate quote delimiters. SELECT InfoTable.SetID, DSum("Qty","InfoTable","SetID='" & [SetID] & "'") AS TotalQty FROM InfoTable; This would normally be done with an aggregate query. SELECT InfoTable.SetID, Sum(Qty) AS TotalQty FROM InfoTable GROUP BY SetID; Much...

The "conventions" are not important especially the nonsense about prepending field names with a datatype. What is important is that the names are meaningful. It would be a waste of time to change them unless they are meaningless. If you do need to change any names use the Replace facility in...

Please elaborate the kind of standards are you talking about.

Access probably isn't going to like decimal(18,2) because it has no equivalent. decimal is a scaled integer and I doubt Access would handle an 18 digit integer even inside a decimal. The values are money so why not use money datatype?

How do you feel about children having the right to make a decision to take puberty suppressing substances. presumably ones that have no permanent effect once discontinued?

I don't have Access at home so I've not looked at the file but good practice when recording status of a process is to use a sequence of numeric codes to represent the states. Don't record the names of the states on each record. The names corresponding to the numeric states are recorded in a...

The year being in the table name makes me think the whole need to add the constraint stems from some kind of archiving that you are expecting users to do at runtime. Wrong thinking. It is a dangerous process that should not be done routinely. Why are you creating archive tables? If you have...

The displayed values belong in a lookup table against a numeric key. Join the table to the data so the displayed value is directly available from the table.

Have a look at how a similar problem can be addressed much more elegantly without the insert queries. https://www.access-programmers.co.uk/forums/threads/data-input-from-a-query-and-user.287096/#post-1489938