Search results

You could give a Compare/Diff program a crack at it with Binary matching turned on, but I'm pretty sure you'll get garbage output... :banghead: Only other thing I can think of is open the two side by side and compare Last Modified dates on all your database objects. That might at least narrow...

It looks to me like the 'rule' might actually be that the workweek with X/1/201Y is the full week that starts a fiscal month, and your fiscal calendar starts June 1. Would that be true in other years, or is it a quirk of 2013/4? Also what happens if the 1st is a Saturday/Sunday?

This is still the answer then. You cannot easily go back and retroactively figure out which is newer without examining your code/tables/forms, but this will make it trivial going forward.

Not plain enough. WHY do you want today's date to be zero, rather than Date() automatically prompted? WHAT do you want to do with a day ago, and a week ago, and why can't they be autocalculated from the first datefield? We're trying to help you. Help us help you by giving us good information...

Can you explain in plain English what you are trying to do? You can autocalculate a lot of dates based on Today() or the input in your 'first' date field. The DatePicker I am speaking of is an inherent feature of Access 2007+, and will give your user a mini calendar to pick a date from...

You mean two copies of an Access database? Put in a tableVersion and update it any time you update the db structure (1.0, 7.1, etc). Make sure it's in the front end, not a linked table.

The [#] button in the post editor will wrap your data in the tag so it's equally spaced and easier to read. I have taken a stab at reparsing your data by hand, see below and fix as necessary. month period table compl date range1 compl date range2 fiscal month completion 4/29/2013...

Note: Cronk is kidding here. You should start drinking before attempting this. :banghead::D

That might be more readable if you used the [code] tag instead of [font].

Just a stupid question, are you looking at the report in Print Preview mode? I've found that Format will not necessarily trigger in Report view.

Text fields in Access 2010 and later can go up to 255 characters, if you change the field size. Would that suffice? It's not clear if 176 is average, standard, or high.

Not a clue. In any Access form, Ctrl+; will input today's date, but i don't know of shortcuts for the others. You could do it via code, but why not just use the DatePicker?

No problem, glad you got it working.

The problem with some Christians is they just MAKE THINGS UP rather than admit they are wrong. The KJV did nothing of the sort, it's a Christian-focused retranslation of earlier Jewish translations and Latin manuscripts, commissioned by a political leader to support HIS church in particular...

...put it in the BeforeUpdate event of all of your data entry forms?? :confused: There's no field names or form-specific code there, so it should be totally portable. I'm not sure why you want to do this, as in my experience users often click the wrong thing when presented with extra choices.

rInvoice looks at [FORMS]![DATERANGE].[TEXT10] And [FORMS]![DATERANGE].[TEXT12] in one place, but the free parameters [BEGINNING AFENO] And [ENDING AFENO] in another. Put all the fields into your DATERANGE form and you'll avoid the multiple entry thing. Also, this probably isn't your current...

Can you upload a stripped-down version of your database? You'll have to ZIP it up because you have less than 10 posts... just remove any confidential data, and only leave enough records to show what you want to do.

Have a form that only the Co-Op Coordinator can open, and put your bound SSN field there. Everywhere else you can use the calculated munged version. Just turn off the navigation pane and all but your cleverest Managers will not be able to find your tables. :)

Help is your friend. http://office.microsoft.com/en-us/access-help/dcount-function-HA001228817.aspx It'll be something like:=DCount("[CaseAgeField]", "tableName", "Between 8 and 36")

Do you need to "enter" it on the form? If not (say, only the DBA will be entering it behind the scenes, directly into the table) and it's just for display, you could make it a calculated field:="###-##-" & Right([SSN],4)