Recent content by fhs

I'm working with a fairly old financial application (converted from '97 to 2007). Unexpectedly, the application suddenly isn't loading and I'm getting a "Run-time error '-2147217838 (80040e52)': Data source object is already initialized." What is going on? This worked a week ago! Here is the...

The 'six-digit' Autonumber (incremental) is the actual "Stock number" of the item for which there is a record. For whatever reason that the application has skipped several series of Autonumbers, I would like to identify them and develop a way by which they can be used before we get to the end of...

I agree with your point. I really did a crummy job explaining the situation. Here it is, my department has used an Access '97 db over ten years, but recently converted to '07. The Autonumber field which provided the record number has skipped a number of times thoughout the use of the...

I have a db with over 87,000 records. Each record has an Autonumber ID. I do not believe any records are missing from the db, but there are some "skipped" or missing Autonumbers. How can I query this table (the only table with Autonumbers) to identify the missing numbers? Thanks ahead of time.

Thanks for the code, but it's still not working properly. The pop-up message is displayed despite a double-click in the txtClockInTime or txtClockOutTime. This shouldn't occur. I'm returning the zipped copy. Thanks for your assistance with this mechanism.

Do I place this code in the BEFORE UPDATE event of the form or in each of the fields (Clock_In and Clock-Out)? I tried in the form's event and now I am unable to save the record. Any advice?

I appreciate you discovering the faulty record. Can I prevent a record like that screwing up the query or is there a way to restrict the user to populating only one field in the frmClock-In Clock-Out?

Bob Larsen initially helped me with this report and I hope he is available to look at again. The Director's Report button opens a parameter form requiring a Begin date and an Ending date to query start and end times for employees. This application has run well for the past two months. However...

You nailed it! Great job! Thanks so much for your insights.

It does work! It works GREAT! - until I print the report. The date parameters appear on the screen, but when I print the report I get #NAME? in each text field. Hazard a guess about that. Otherwise, this really meets the user's expectations - for now. Thanks Bob. Lemme know if you have a idea...

I think you may have returned the wrong file. The Zip file and originally enclosed in this post was Clock-In Clock-Out EXPERIMENTAL.accdb. Is that the one you looked at?

The central form in the app is "frmClock-InClock-Out." The date parameter form is "frmReportDatesToo." The resulting report is "Employee Time Report."

In previous posts, I have received tremendous assistance from the forum (especially Bob Larson) with respect to generating a report with parameters. Recently, the user imposed an additional requirement, requesting that the specified dates (from the parameters) be inserted into the report header...

Thanks again, Bob.

I've worked on this with Bob Larson before and I really hope he's around to take another look at this. There is a parameter query for dates (XX/XX/XXXX) that select a fortnight range to generate a report. It has worked before... now it's not working. Also, the form that generates the data is not...