Search results

thanks for the recognition >good luck with your project

good luck with you project >thanks for the like reaction

several ways to do it >try this way >use query to sql SELECT [PhysicalTherapy].groupyear, First([PhysicalTherapy].sessiondate) AS FirstOfdate, Last([PhysicalTherapy].sessiondate) AS LastOfdate, [LastOfdate]-[FirstOfdate] AS diffdays FROM PhysicalTherapy GROUP BY [PhysicalTherapy].groupyear; >but...

quite hard >address, city, state, and ZIP code. >using "BeforeUpdate" could be possible, where there is 1 field that received your old "address, city, state, and ZIP code" as field1 >could be the other field received your new "address, city, state, and ZIP code "AfterUpdate" as field2 >in a...

>sample codes, very useful Dim strWhere As String Dim lngLen As Long If Not IsNull(Me.SelectPropertyName) Then strWhere = strWhere & "[PROPERTY TYPE] like ""*" & Me!SelectPropertyName & "*"" AND " End If lngLen = Len(strWhere) - 5 If lngLen <= 0 Then...

wow very prompt >add this to my filter mode Dim strWhere As String Dim lngLen As Long Me.Filter = strWhere Me.FilterOn = True

welcome tammy >express out your vision for sure you shall meet the best result with your own way >thanks for the like response

very important data banking >if for this year you can make SplitTable for that as your server for 2020 attendance >well for 2021 separate SplitTable set on your link table manager, i used this method cause i also have data banking over 10k >on the run your 2020 SplitTable for 2021 is unlinked...

hi nice query run >try the sql of query below SELECT Table1.PartNumber, Sum(Table1.SumOforderedqty) AS SumOfSumOforderedqty, First(Table1.orderdate) AS FirstOforderdate, Table1.PartNumber, Last(Table1.orderdate) AS LastOforderdate, First(Table1.SumOforderedqty) AS FirstOfSumOforderedqty...

quite tough >your field [Line Status] should have a partner fieldname ="CountRecieved" then if [Line Status] = "Received" then [CountRecieved] =1 >with that dataflow [Text35] = Sum([CountRecived]) >try that simple way, i used it with my complex Forms

look at your num2 2. calculate a weekly attendance (in total hours) for every staff in the list > your "Attendance (in hours)" if this refers to one day may that be on your report sumtotal "(in total hours)"

add 2 fields >time of log in and time of log out >in order to determined "Attendance (in hours)"

3 fields were given > no worries > would be: [Full Name]=[Last Name] & ", "& [First Name] > on [Last Name] and [First Name] update insert code above

we can still use access but more likely the updates be limit > Mainstream support for Access 2013 ended in 2018. Extended support will end in 2023. > isladogs mention "If you have a license for 2013 you will still be able to use it once the support period ends (in 2023?)" > Access 2016...

sorry >i only sight the concept >yes codes has complete syntax for that (i always use it) >wish you could arrived with it (only you would consider the other form functions) >but if you want the specific syntax maybe i could share it later

wow nice play >form timer is great >why you set IDLEtime and ExpiredTime idleminutes value is undetermined, if this run "If ExpiredMinutes >= IDLEMINUTES Then" just setting this "ExpiredTime = 0" for DoCmd.Quit acQuitSaveNone >if your time expired >=idle maybe set dim answer...

You like Access much >on the run i use 2010 if my system break's down >2013 has nice feature and mangeable too >i try 2019 but i can't work with well, there's limation when setting up >as of today i keep on 2016 but indeed some controls don't work anymore, but i remain with 2016 >sure if 2013...

good luck smig

good luck >with your project, you can do it, all the way

GUESS >That is auto run >maybe supply also the cmdsave codes if applicable >when you insert that ontimer always run for save to table >that if your acForm settings is true to your target actable >i used it many times >well in this case, supply your codes to ontimer, if you have use calculations