Search results

Hmm. Not sure what to suggest I'm afraid. I've just tried running a simple union query against a couple of ODBC linked tables in a Sybase database, and had no problems. Sorry I can't be of any help. Matt.

I can't see too much wrong with the SQL. You don't need to use the AS statement (i.e. "AS CountOfRM09SQ") anywhere apart from the first part of the query, and I'd have UNION & SELECT together: I.e. UNION SELECT .... Not Union Select Try correcting those, and if that doesn't work, I'd...

Are you running SQL pass-through queries, or a normal query on a linked table? Can you post the SQL?

Try: IIF([SecondDateField] Is Null, #31/07/2003#, [FirstDateField])

Sounds like you need to have the Location table in the query twice. In the query window, assuming your Activity and Location tables have a normal 'inner' join, add the Location table in again (it will be called Location1). Create a join from the subscription location field in the Activity...

The problem is that when you remove that line of code, all the routine is does is create a message, but doesn't do anything with it. Try replacing EmailSend.Display with EmailSend.Send HTH. Matt.

:confused: :confused: Not sure I understand what you mean. Are they DOS commands??

The code I used is: ----------------------------------------------- Public Sub sListTables() Dim tdef AS TableDef For Each tdef in CurrentDB.TableDefs Debug.Print tdef.Name Next End Sub ------------------------------------------------ Then I just called the routine from the debug window...

I used some code to run through all the Table Defs and print the name in the debug window. Included in the list were the hidden system tables (i.e. MSysAccessObjects), but when I go to options and make them visible, there is one from the list that does not appear: MSysCompactError I am having...

Ever figure this out?? Has anybody figured out a cause for this yet?? I'm having real problems with this at the moment - exactly the same scenario as above. Split db, with all users exiting the FE correctly, and then for no reason it needs repairing. I've had this happen 4 or 5 times in one...

Hmmm, that old chestnut... I have experienced this very same problem before, and think it may have been a size issue. The databases I had this with I was using to re-organise data, and as such was importing and exporting vast amounts (the db's quickly excalated to well over 500mb). The only...

Everything I've learnt has come from a combination of three things really: 1) Attending courses 2) Books - (like "Access 97 - Power Programming" - fantastic for VBA) 3) A lot of Trial and Error!! The best way I found to get to grips with SQL, is to create a query in the normal fashion, and...

Assuming that whichever database you want to run this in has links to the check_history tables in each companies database, you could run a union query. i.e. SELECT DISTINCT company_name, employee_name FROM check_history_1a UNION SELECT DISTINCT company_name, employee_name FROM...

Whenever I've had this problem in the past it's because I haven't set the Column Headings property in the crosstab query Matt..

Bit more info, & another question! Ok, the .exe file seems to originate from a freeware program called AutoIt - www.hiddensoft.com/AutoIt Currently, I just trigger the .exe and leave it running, so that when the scheduled DB kicks in there are no problems. I was going to try and trigger the...

???? Not sure what you mean. I know very little about this .exe file, my skills being Access only unfortunately. Obtained it from a colleague who also develops Access, and it was written for him by somebody that has now left the company. When triggered, it just runs in the background. The...

I have a database performing various tidy up/admin routines, which is scheduled and run very early in the morning (6am). I wanted it to fire off an e-mail to a few people to confirm when the routines had successfully run, but ran into problems with Outlook opening up a security message ("A...

What about: wphonestd: Trim(Left([Workphone],InStr([Workphone]," "))) wphone: Trim(Right([Workphone],Len([Workphone])-InStr([Workphone]," ")))

Many thanks Colin. Have amended some of the code from that site to suit my needs and it works like a dream. Thanks again, Matt.

I encountered a similar problem (calculating working days) when designing a Absence/Holiday database, but encountered problems with National Holidays (i.e. Xmas Day - obviously not a working day but could fall on any day of the week). Any ideas on how the above function could be amended to take...