Replies

As ejecting the disc while Windows is rebooting worked just fine, I have been searching to find another way to eject the mini-cd or why it did not eject. The only other way I have found to eject the mini-cd was to disable the device from the device manager in the control panel and then press the eject button.

I did not find a good reason why the device would not eject except from this post from Microsoft http://support.microsoft.com/default.aspx?…kb;en-us;231814 [/url] As their solution did not work it was the closest thing I could find as to what was happening. As the camera’s instruction manual labeled the CD port as removable media along with the memory stick (which I will use from now on).

Winston

Thanks, that worked but just curious on what would cause it to not eject normally though.

Thanks guys

The Me.combo0 = Me.combo0.ItemData(0) Works perfect.

Winston

Hans,

The combo box does not support this method or data member but a list box does.
I want to remove the previous selected value from the combo box as it may no longer be the correct choice.
I thought by selecting the first value in the combo box was the easy way of doing this.
I added a database that creates the same error as the one I am working with.

Thank You,

Winston

Jeremy,

DoCmd.GoToRecord , , acFirst

Try adding this on the event to go to the first record based on the form its self. Also you could try to do a Me.Refresh after setting the visibility to true.

If you mean selecting the first choice in the list box then use
Me.lstNames.Selected(0) = True

Winston

Scott,

Create an unbound form with two unbound text boxes one called start_date and the other called end_date. In both of your queries set the date criteria to “Between [Forms]![your_form]![start_date] And [Forms]![your_form]![end_date]” Also set the format property of the text boxes to short date.

Do not use the ” and where it says [your_form] put the name of the unbound form you created here. Then add a command button to execute your macro. I am assuming the both the OutputTo Action and Update query runs from the same macro.

Winston

Hans,

Thank You, that did the trick.

Winston

Hans,

Here is a copy of the database. The Line Hours field is the one with the decimal point formatting issue. Just run the report from the command button on the frm_main.

Thanks,

Winston

I went around to four different computers here at work and could not get the error to occur. There might be someone messing around with the database so I would set the popup and modal property on the splash form to yes and the close button property to no. In stead of using a Autoexec Module, use the starup

While watching a recording of Monday Night Raw at home I sat down and recreated the database to attach to this post. I discovered at home what Hans had posted worked perfect. I went to work the next day thinking it worked at home, so it should do the trick. As I probably just have a spelling error, but it did not work. The only difference is I have 2000 at home and 2002 at work. Not seeing how that could make a difference, I tried a little different approach. I finally got it to run properly at work. Thanks for the initial help Hans, as it showed that I was trying to do something that could be done. Here is a posting of it just incase it can help someone else. Note that Hans

Hans,

Before it would tell me incorrect syntax, now I get a Run Time Error ‘170’ Line 1: incorrect syntax near ‘2’.
I will take the database home tonight and make it small engough to post as I am sure having it would help.

Thank You,

Winston

Hans,

Once again you are a life saver; I was going nuts trying to figure out why I could not set the focus back. I thank you for the advice and your time.

Hans,

Using your solution that you provided like in the post 473938, I was able to solve that problem. I still do not understand why the setfocus does not set back to the control on the sub form.
I have tried the solutions from the Microsoft knowledge base and I do not see where I am going wrong. I can get the focus to set on the main form and even the nested sub form on the sub form, just not in the subform itself.

Thank You for the help on solving the initial problem as it works like a charm.

This was a good solution, and I understand what Mark Liquorman was saying and already planned for it. This was just a sample of what I was using as I have before update event as well with the same problem. Why can I not get access to set the focus back to that field in the subform? I can do it in the main form just not the sub form to catch any left out fields and duplicating errors before they happen. If you have any other thoughts or if it is even possible, might just be limitation in Access.

Thanks for the input

Thank You for your help using DCount did the trick.