Search results for query: *

I am researching the intel dual core processor trying to find out if it will help dealing with large queries processed locally...now Intel says it will help if the application is multi-threaded....Can someone shed some light here...I doubt access is...but who knows.

I often link to DB2 tables via ODBC... sometimes the tables are large and the queries can be slow. I understand that the query is being processed locally and all that...many times I can't even alt-tab to do something else. I don't care if the query takes some time to process, its sitting there...

I have a daily rtn which imports a csv file. I am able to import the table manually, however when I run my docmd.TransferText statement, it fails on err#2391. The field that 2391 displays is a wacky name... I use the table struct from the manual import and I still get the error message. So, i...

I have an excel macro that my access app calls. All it does is delete column A from an attachment as a daily cleanup process. After it runs, it prompts with "save, no, cancel" prompt. If I am out, nothing else runs because the prompt. How can I handle this? (I go on vacation in 2 wks!!!!!!!!)...

I need to change the behavior of a group of 6 radio buttons. Management want the behavior to be, instead of only 1 being enabled, they could click 2,3,4 .... SO, instead of only 1 being selectable, the user could select 2 or 3 or whatever. This is an EXCEL form. Thanks

I am trying to get a macro to rename a table with the name and concatenate the month and day....so I want the rename macro to take BSC151 and rename it to BSC151-0801. I tried something like this...BSC151 & Month(Date) & Day(Date), but it took it literally and did not expand it. Any ideas.

Is there an add in for access that will group/and document queries. I suppose this can be done in several ways...i am interested in ways you all document your queries.... thanks

I have a parameter query that is invoked from a form... If the user clicks cancel from the parameter query...they get an ugly kind of message...is there a cleaner way to exit a parameter query.