Happy new year everyone!
This probably isn't worth anyone's time but i am stumped and a bit annoyed...
I have just made the jump from 2003 to 2010 with a large database and am getting to grips with everything (a bit easier than expected to be honest)
However the view i am used to for database...
Thanks so far.
DAO 3.6 and Office 2014 database engine references seem to conflict so which should i be using going forward?
2003 didn't have a problem with this but i accept things change.
I have replaced all instances of "AS Recordset" with "AS DAO.Recordset" and that seems to work OK now...
I feel a bit stupid because i'm sure the answer is right in front of me!
I'm behind the curve and looking into upgrading a 2003 database to 2010.
I have not messed with access for a long time so am out of my comfort zone with 2010.
I've let access save the front and back ends in 2007 format...
Hey jdraw that's a good list!
Well worth working through as it left me feeling like my indexing is pretty poor, even though up to now it's worked fine.
The users have copies of the front end on their local machines.
Occasionally I have created a new backend and pulled the existing backend...
I'm using Access 2003 over a 100Mb network.
The back end is about 100Mb and the front end is about 10Mb so nothing too big and they are compacted every few weeks to keep them trim.
When the back end isn't being shared it opens pretty much straight away over the network (about a second).
As...
I have looked briefly at the list of deprecated items and to my total surprise so far there are no big shocks! Looks like decisions such as building my own calendar rather than relying on the control were a good move after all!
If only Microsoft knew how good access was! It should be aimed...
Thanks for the reply Pat.
I kind of thought I'd end up looking at A2010 running on Windows 7.
I'm interested to see what A2013 has in store but I suspect jumping to that without facing conversion issues is more than a distinct possibility.
Ironically for a microsoft product those of us who...
I am running a split Access 2003 database (as part of Office 2003) under windows XP.
I know I should have moved to windows 7 and Office 2007/2010 well before now but I'm looking into all upgrade options at the moment prior to support for windows XP being discontinued in 2014.
Since support for...
Thanks guys.
I have checked the form and set the button as the default to run the code when enter is clicked. The code was in the on click event in any case, the on got focus event just clicked the button.
I've got a "thing" about relying on "one offs" like this in that they're not available...
I hear what's been said with regard to putting the code behind the on click event but if the button can't be the default button doesn't doing that mean the user has to press enter twice, once to move the focus to the find button and then again to click it?
The form is a multi use search tool...
I reckon i must be losing my marbles or i'm just being lazy (probably the latter).
I've got a product search form with a text box (for the search string) and a "Find" button to perform the search when clicked.
The user types a string then clicks enter. The focus moves to the find button and...
I must be missing something but the product shots i'm seeing of access 2010 seem to suggest that you can conditionally colour text within a form field.
I have a DB containing many records and i would like to be able to use colouring to highlight specific types of record within search results...