Search results

I have one of my work screens in portrait for that particular reason to be able to see entire sqls, views, functions, packages etc.... I always get remarks about having my screen the wrong way.

have you not noticed yet? There is a bug in windows that screws up the Fx keys, swapping the F5 and F8 is one of the known problems as are the F2/F11 and F3/F12 ... reason for the bug as yet is unknown. Personaly I do also seem to experience problems with swapping of Page up and Page down...

Give it a try and find out.

You could do something if the venue were split into columns instead of rows... SELECT Matches.League, ScorecardBatting.batsmanId , SUM(ballsFaced) AS ballsFacedByLg , SUM(iif(venue = "X"; ballsFaced;0)) AS ballsFacedByLgVenueX , SUM(iif(venue = "Y"; ballsFaced;0)) AS ballsFacedByLgVenueY ...

Simply create new query, adding the two above stored queries, joining them and selecting the data you want?

Wasnt refering to you @Pat Hartman , rather to the person you responded too :)

How about not responding to a thread originaly from 2009 ! 11 years must be some kind of record?

You are best off creating a log TABLE, instead of trying to log changes into a single text box.

DoCmd.OpenReport "rptMonthlyReportFlagging", acViewPreview, , "x ='" & dMonth And "' y ='" & dYear & "'" Seems to be missing a little something ... DoCmd.OpenReport "rptMonthlyReportFlagging", acViewPreview, , "x ='" & dMonth & "' And y ='" & dYear & "'"

I believe that feature works when you click on anyone's name and choose "Ignore"

All hail rule #1 from all mighty @Pat Hartman It is good to follow this rule :)

Concure... Expr4: Mid([Installation Date1],3,2) & "/" & Left([Installation Date1],2) & "/" & Right([Installation Date1],2) In order for you to get 1119/11/19 you must have not used the above formula.... instead... Expr4: Mid([Installation Date1],3) & "/" & Left([Installation Date1],2) & "/" &...

250918 = 25/0918/19 Doesnt make sence! and quite honestly is impossible to boot. 11012 is possible to fix, however how does your number date work in may? 1512 or 10512? The best way to handle this situation is to make a "tblDate" that holds your numeric date in one column and the "real date"...

Fairly simple solution, to add to @MajP Have a PK in your qryTrue... then in your qryFalse you dont need all kinds of difficulties to find nulls etc.... it can simply be: Select * From sourceTable(s) where PK not in ( select PK from qryTrue ) Only troubles you may then run into may be due...

I find people want to use "high tech" and "new stuff" just because it is "better" or "newer", mostly the latter. However nothing beats a good old excel sheet or a quick access db for a nice steady fast and cheap working solution.

It makes it easy to find "real" threads that I am involved in already that have reactions that I have not seen before... Potential questions or answers from the OP .... or other ideas from fellow posters on the forum who may have other ideas or solutions than the solution I offered....

My favorite page: https://www.access-programmers.co.uk/forums/find-threads/contributed I dont post (much) in the cooler

No no no. we do not design tables with itterating columns... mon tue wed etc is an itteration of days/dates.... thus this is bad design. Instead you should desing a table that simply holds the date and time worked, preferably in a TIME and/or datetime format. Concantinating information...

"not ideal" you mean NOT POSIBLE. Any query by its nature is a random fetch from the table(s), it will 99% of all times return the order data was entered in the table, assuming only one table is used, with joined tables all bets are off.... however even with 1 table, it is no guarantee to any...

This is why your primary keys in tables are always hidden from the user and always are auto-increment numbers and always are in their nature meaningless to anything but your database. At anytime you find yourself using a PK or FK for anything but this.... adding meaning to these numbers, step...