Search results for query: *

How about checking the concatenation of the Date and Tme? That is: #3/15/05 23:59# is earlier than #3/16/05 3:00# Checking Date & Time should always yield a correct result. Does that make sense?

As long as I'm understanding all this correctly ... With text box control sources set to: =cboFlightNum.Column(1) =cboFlightNum.Column(2) =cboFlightNum.Column(3) There is no need for the AfterUpdate statements: Me.TxtAirlineName = Me.cboFlightNum.Column(1) Me.txtSchedArriveTime =...

You'll need to use the VBA commands Dir, ChDir, ChDrive. You may be able to get away with just the Dir function. Syntax: Dir[(pathname[, attributes])] with attributes being optional and pathname required (will accept wildcards. Access Help says: "You must specify pathname the first time you...

I would use T-SQL on the server, either through a SQL stored procedure or an Access Pass-Through query in T-SQL syntax. In my experience this is fast, easy and SQL Server manages the temp tables on a per user basis. SQL Server help has this to say: "SQLOLEDB exposes the...

Cascading is setup on the server. Boy, do I feel stupid (bouncing heel of hand off forehead)! Somehow Autocorrect was turned on in the backend DB which slowed Updates. Because of that we weren't waiting long enough. The cascade WAS happening, just veeeery slowly. Thank you for your attention.

There is a stripped down version you can install on users machines that allow them to run Access apps but not create them. It is called Access Runtime and is free. Check the Microsoft site for how to get and install the Runtime.

Is it possible that your printer settings are set to "print direct to printer"? It sounds like the print data is not going through your print queue, but direct to the printer. This will not release the system for new threads until printing is complete.

Here is code I use for a menu item that only appears for DB users identified as "Superusers". Note the Allow/Disallow Bypass setting requires creation of that Database property first. The code is in Access help. Public Function EaseStartup() With CurrentDb .Properties("AppTitle")...

I'm having the same problem in V2003, but only on one workstation. When I point to the distribution copy on the server, it runs fine. There is no ldb file, so noone is using the local DB. Just out of curiousity, are you by chance also having a sudden problem where cascading updates don't cascade?

Cascading updates suddenly stopped cascading. This behavior may have started after the installation of Access 2003. The problem relationship is between Client and Services tables using the Social Security #. Application is client/server, built in ACC2000 and is still in that format of...