Search results

I had already tried that. I used 'Hides the navigation pane for users who get this as the startup screen DoCmd.NavigateTo "acNavigationCategoryObjectType" DoCmd.RunCommand acCmdWindowHide 'hide the tool bar too DoCmd.ShowToolbar "Ribbon", acToolbarNo ...in the current event of the startup...

Hey all, Just converted over to Access 2010 and there are a few things that I can't figure out. I use dual monitors for design and the 2nd monitor is for the code window and properties panel. I can't figure out how to get it to use the 2nd monitor. I can resize the program window all the way...

Well, I made the move and am using Access 2010 now and I am running into a couple issues. First off, I want to get rid of this menu on startup: Not sure what it's called (ribbon, menu bar, etc). I am able to hide it using DoCmd.RunCommand acCmdWindowHide DoCmd.ShowToolbar "Ribbon"...

I guess the remaining question is WHY it has to be done this way in order to work :D All of the other ways seemed logical but not to Access.

jdraw, that last one did the trick. I have tried everything even within a function, all sorts of manipulation of the data to make it into a date and I kept getting the same error but yours finally worked. Thanks!

jdraw, the query you created will work but try putting <Date() into the criteria for that field and I believe you will get the error What's most puzzling is that you can fill that field with a string value of 12/12/2050 and when you use CDate to convert it to a date type and compare to Date()...

It has everything to do with comparing the field to a date type. I can set up a select query with this field: CDate(Nz([Hold_Expiry_Date],"12/12/2050")) And it displays as it should, but as soon as I attempt to compare it to Date() I get the error. It seems that CDate is not converting it to...

That first resulted in invalid use of null errors, and when I added Nz then the dreaded type mismatch error came back. The blank fields are definitely null.

I even tried this IIf(IsNull(Hold_Expiry_Date), Date(), CDate(Hold_Expiry_Date))<Date() and I still get the same error

The error has everything to do with the field being null. When I filled all of the records with a date value in that field there was no error in running the code.

I still get the same error when I try that :banghead: The intended default can be anything that is today's date or greater. I have also tried Nz(Hold_Expiry_Date, #12/12/2050#) and I still get the error.

This is a strange one. Initially this code worked, and then it gave me the error, and then it worked, and now I am getting the error again. I have a text field in a table that will either be blank (null) or contain a date in the format mm/dd/yyyy. In my query I am trying to get all records...

Thanks for the info. It's good to know what I am facing by making the change. I have been meaning to change all of my code to late binding because I have had issues in the past with missing references. Just haven't gotten around to it yet but now is a good time.

There are some tables in the front end but they are either for temporary data or static data. None of them are linked in any way to the main table that I am having the problem with. When the update is downloaded, the table from the downloaded mdb (tb_Jobs_Update) is transferred into the front...

I guess it's time to get with the times here. I have been using an Access 2000 DB for many years and the owner of the company wants to upgrade to 2010. Is it correct that I can run it as is (MDB) in Access 2010 without a problem or would it be advisable to convert it to ACCDB? This DB has a...

OK I kind of figured out what is happening and maybe you can explain why. There are 3 users of this database at 3 separate locations. The main user does all of the data entry and changes and the other 2 use the data for reference. I have it set up that once a day the main guy uploads the most...

Let me try to explain further. This is a standard form and the record source is the table. When you add a new record using the form (no query involved) there is a conflict in the autonumber field because the autonumber index on my computer is different than the index on his. Say there are...

Anytime a new record is written to the table it is done through standard form data entry. I use append queries all of the time but in this case it doesn't help.

It works fine with his data but when I test new features or changes by attempting to add a record I get an ID conflict error message and I can't proceed.

The database actually does have a back end with linked tables. I don't have all of his data, maybe about 20% of it for testing but wherever my primary key index is set falls right within that data