Search results

That's because a Subform is a Control on the Main Form...and if AllowEdits on the Main Form is set to False...you cannot Edit any Control on the Main Form...including the Subform Control. The Access Gnomes consider doing anything to the Form that occupies the Subform to be editing it. Linq ;0)>

'Copy/Paste' is not the same as 'Cut/Paste!' When you place the cursor over the appropriate Page its background will change color, indicting that you'll be Pasting to that Page. Linq ;0)>

I can't open your db, I only run v2007, but in v2007 testing shows that in order for the Record to become Locked immediately after 'Closed' is selected, you'd need to Save to Record immediately after changing AllowEdits : Me.AllowEdits = Me.cmbStatus <> "Closed" If Me.Dirty Then Me.Dirty =...

This just reinforces the need to check for missing references! When a Function misbehaves...especially a Date/Time related Function...a common cause is a missing references. The appropriate Library is probably loaded in the working box...but has never been loaded in the new laptop. Also...just...

Glad we could help! Good luck with your project! Welcome to Access World! Linq ;0)>

Sure...on each appropriate Form simple use: Private Sub Form_Activate() Me.Detail.BackColor = vbBlue End Sub Private Sub Form_Deactivate() Me.Detail.BackColor = vbRed End Sub substituting your own preferred colors. Linq ;0)>

Have you checked for missing references? Linq ;0)>

Doing this kind of thing is always going to be complicated...there's no getting around that! Don't quite follow your scenario, here, but to be honest...your data scheme seems flawed...appearing much more like a spreadsheet than a database. Linq ;0)>

What are you using as the Control Source for you calculated, unbound Control? The number of Records in your Subform, whether they are less in number than your Subform can show at one time...or more in number than can be displayed at one time...should not make a difference! Linq ;0)>

Sorry, Micron...missed that in reading your post! Linq ;0)>

Also understand that if you get this to work...it's going to do the Conditional Formatting based on the Record that currently has Focus! In other words...if the first Record has Focus...and you hover over your Control on the 5th Record, without first moving to the 5th Record and giving it Focus...

Mike is correct in not using an Autonumber field for this! My only differing with his advice is that the code should be in the Form_BeforeUpdate event...not the Form_BeforeInsert event...unless this is going to be used in a one-off database by a single user on a single machine. If this is in a...

Indeed they are! My first box (can't even remember the make) had a 20 mb hard drive and DOS...was pre-Windows...by about three years, as I recall! First project was a relational database for work, written in QuickBasic...and something as simple as adding three months the current date took up...

I see comments about don't use this function because it runs too slow...or don't use this approach because it's a resource hog...and think that it often does, in fact, go back to the days of 128 KB of RAM, with lightning 10 Mhz clocks...and has nothing to do with today's machines and their...

Running the code in your posted file...using """ & Me.OpenArgs & """ with 3 Double Quotes, on either end produces & Me.OpenArgs & in the Control, as I said...not the appropriate DocRef. Linq ;0)>

Surprisinghly...what you just posted does, indeed, work! As well as my code """" & Me.OpenArgs & """" but the original code, which was co-opted from Access Help, was " " " & Me.OpenArgs & " " " with three Double Quotes on each end...which doesn't work, as I noted...instead of Double Quote...

Knew something didn't look quit right...actually that has to be Me.DocRef.DefaultValue = """" & Me.OpenArgs & """" or else the Default Value you'll end up with will be & Me.OpenArgs & not the passed value. Linq ;0)>

In the secondary Form, try moving your code to the Form_Load event, instead of the Form_Open event. Generally speaking...Form_Open is to early to try doing any type of data manipulation. Linq ;0)>

I would think that the definitive question, here, should be what, exactly, are you trying to accomplish by calling the OnLoad event of another Form! That aside...to reference anything on a Form...the Form has to be Open and (I believe) Visible. Linq ;0)>

I once wrote a hack for this, as have others, requiring the use of three or four events...to make the prompt appear...then disappear when the Control is entered, etc...then checking, in the Form_Before Event to see if the prompt was still populating the Textbox...if so, setting the Control's...