Recent content by kessmiller

Thanks for the ideas. It looks like the main issue was we needed to install a new driver for our ODBC software. I still have several questions about this, but will talk to others on our staff about those.

SELECT Table1.Field1 FROM Table1 WHERE (((Table1.Field1)<[enter date mm/dd/yyyy])); Table1ID Field1 1 10/15/2012 2 3/1/2012 3 5/15/2013 4 11/1/2013 Is your field defined as date/time? this worked for me. If field is defined as text you'll need different logic.

We are in the process of bringing up a new server. We have a number of Access db's connected via ODBC to the old server. We need to change these to point to the new server. I thought we should be able to go to the Control Panel/Data Sources (ODBC) and just change the server ip address from...

Thanks Bob! Changing the name of the procedure fixed the issue. My other procedure that worked was actually named differently - one had a dash and the other an underline. I knew it was stupidly simple! What is the difference between standard and report/form procedures?

I have a macro that runs several steps and then I want it to export a file to text using a spec. The specs no longer work in the macros so I wrote a module to do the export. I can't get the macro to call the module correctly. I've broken it down to just the one command in the macro calling...

I think this is exactly what I am looking for, but want to make sure. I work for an insurance TPA and am working on a database where an entry will be made when someone needs a new card printed. After entering 20 people for example with 4 different plans, we want to run a macro to print the...

OK. Big duh moment. I had not installed the ODBC links needed on my users PC. They're on mine, so I didn't think of them. Thanks for pointing me in the right direction. How would I edit the switchboard messages to be more informative? I'm not too great on the coding side.

I have a database that I created in Access 2003 that creates a report. The report runs fine when I run it on my computer using Access 2003, but gets and error 'There was an error executing the command.' when I try to run it on another machine running Access 2007. I don't know where to look even...