Search results

Pas d'elle yeux Rhone que nous.

'Every great man nowadays has his disciples, and it is always Judas who writes the biography.' Oscar Wilde - Intentions (1891) ‘The Critic as Artist’ pt. 1

I understand that. My comment related not to maintaining an unbroken sequence, but to filling gaps in a sequence caused by the deletion of prior rows, or aborting the entry of a new row where the key is an autonumber. The ability to replace a 'missing' row with with another with the same key...

As you've touched upon the subject of filling gaps in a sequence of primary key values, I've never seen the point of this, but some people do seem to have a horror vacui. For them the following query is from one of my demo files : SELECT ProductIDs.ProductID FROM ProductIDs LEFT...

Date supports that in the context of the theoretical model. He points out that for a tuple to be updatable there would need to be such a thing as a tuplevar (tuple variable), which there is not. While he is using the terms of the database relational model, in this case I think we can...

Perhaps I'm reading more into George's statement 'It's safer, in most cases, not to rely on AutoNumber sequences' than was intended, but I can recall a number of instances of posts in various forums over the last 30 years where the autonumber mechanism has inserted a value out of sequence. It's...

I agree with what George said in post #6, that relying on an autonumber column to reflect the sequence in which rows were inserted into the table is not completely bulletproof. For a reliable solution add a DateTimeStamp column of DateTime data type to the table. However, do not rely on the...

As far as I can see, you have a ternary relationship type between Albums, Songs and Media, which would be modelled by a fourth table which resolves the relationship type into three unary (one-to-many) relationship types. In an albums parent form a subform would be based on a query on the table...

The following little function will return the result of an arithmetical expression on time durations as a string expression: Public Function TimeElapsed(ByVal dtmTime As Date, strMinSec As String, _ Optional ByVal blnShowdays As Boolean = False) As String ' Returns a date/time...

Yes. In the query make a parameter a reference to the form using the following syntax: [Forms]![NameOfFormGoesHere]![NameOf ControlGoesHere] You don't need to worry about delimiting the value, but I'd advise that date parameters be declared as DATETIME to avoid their being inadvertently...

Mea Culpa! It should have been: "[JobName] like ""*" & strFilter & "*""" Unlike the use of the single quotes character, this allows for a string with an apostrophe in them, particularly important with personal names, such as my own name in its original non-anglicized form, Cináed O'Siridean.

I've attached a couple of little demo files, one which illustrates how to output invoices as PDF documents, and also shows how to handle VAT or some other form of sales/service tax, the other which illustrates how to consolidate multiple orders or parts thereof (analogous to multiple stays in...

If you wish to filter a form or report on the basis of a substring within a value in a column of text data type, you can use the Like operator and wildcard characters, e.g. "LastName Like ""*"" & txtSearch & """*""" However, this can result in specious substring matches, e.g. searching on the...

The attached file illustrates the use of three functions for returning the accounting year, the date of the start of the accounting year, and the quarter of the accounting year, on the basis of the date passed into the function as an optional argument. If no date is passed into the functions...

That does not alter the fact that they violate the Information Principal. These formal principles of the database relational model exist for good reason. I'm attaching a little demo file which illustrates how to automate the recasting of such data into predefined correctly structured tables...

I'm concerned about all these, presumably Boolean, columns. They are encoding data as column headings. A fundamental principle of the database relational model is the Information Principle (Codd's Rule #1). This requires that all data be stored as single values at column positions in rows in...

If you take a look at my reply in Post #9 you'll see that the RowSource for a list box is a query which returns two columns. The first column is the name of the report, the second is a description of the report by which the users can identify the report, and is what the users will see in the...

The following is the RowSource for a list box in a database of enslaved people on a group of plantations which I and my American partner (she did the research, I designed the app) created for a museum in the USA. SELECT ReportName, ReportDescription FROM EnslavedPeopleReportList...

If I were to use a single accounts table I think I'd model the different account types as sub-types in a type hierarchy. That way every transaction, for all accounts, would have a distinct key value.

Coming back to the original topic of this thread, the following two 'append' queries are examples of how aggregated values from multiple transactions in one account can be transferred to a another account in the Transactions table, in this case from transaction numbers 1 and 2, both from account...