Search results

Have you tried looking to see if you have the latest driver? You can find them here: http://support.toshiba.com/drivers

Sounds like your report has something in the HoursMonth report which refers to ME that is not in the VBA window. ME is only good within the context of VBA and will generate an error if used outside of that context.

I don't understand what you are doing with the code: Private Sub cboLocationID_Change() Me.cboManagerID.Requery Me.cboManagerID = "" End Sub Private Sub cboManagerID_GotFocus() Me.cboManagerID.Requery Me.cboManagerID = "" What is the purpose of that? Why would you set the ManagerID to ""...

I just took a look at that file and it showed two records for me when you put in Doe. You have to navigate to the next record.

I had problems in the past. You ask me what. I had changed to renaming so I have not had any ANY problems with any controls or fields in now going on at least 7 years. Since I do not use them I can't specify so I will make this deal. I will not say anything to anyone ever again here about...

Sorry but I don't see it the same way you are seeing it. As I said, renaming controls to something standard and other than the exact field name makes it EASIER, not harder. If you know what you are dealing with it makes it easier when you are wanting to refer to a CONTROL and not the field...

And I don't think you know who actually did because it wasn't me smarty pants.

Never is a strong word. I rename them many times to be able to make things work better. I also rename all of my controls so that they are NOT named the same as the fields so that I know explicitly if I am working with a field or an object on a form/report. So, with a field like ClientID I...

I think I figured it out. You must have a table or query open to do it.

Are you using an MDB file or ACCDB file type?

Fair explanation. That's why it is good to share the WHY you are trying something because we typically are trying to provide the best solutions we can think of based on the needs. A more efficient way would be to not import the tables to db1 at all. Just export them from dba but using db1 as...

Did you put a sort on that field in the report? You need to do so because sorts in Queries don't propagate through to reports.

the Format actually turns it to text, which I'm guessing you didn't know. But how about trying DateValue([FieldName])

It sounds like you either have more than one table in your form's record source, which normally should not be the case. Or you have a field in your table that has a lookup assigned directly at table level, which I would avoid to keep from having issues like shown here...

I assume by hidden text field you mean a TEXT BOX. Fields are in tables and queries (which include form and report record sources) but CONTROLS are on Forms and Reports. You haven't shared much to be able to be specific but essentially, if the record you double click on has the ID field...

In your query you should be able to use CDate on a field and then sort by that created field. Are you sure you don't have any fields sorting before that converted field?

My question as well. What is the purpose when you can just have backups of the database file itself?

Okay, so here's a quick structure which might help. You didn't give really detailed specifics so this is basically just off the top of my head. tlkpTypes TypeID - Autonumber (PK) TypeDescription tlkpLocations LocationID - Autonumber (PK) LocationDescription tblLocationsTypesHeader...

They're still "macros" and they are covered in several books. One of them, Access 2010 Inside/Out, was written by Jeff Conrad and John Viescas (both members of this forum and John is still an MVP and Jeff, who WAS an MVP, works for Microsoft as a Software Test Engineer with the Access Team).

Happy Birthday Jon. Glad you put this whole site together.