Search results for query: *

There appears to be an echo in here... I have done that... I get an error whenever I refer to the connection property of the current project. In break mode the message is Error in DLL, but this is not the first time I have gotten conflicting messages and neither one is really correct. To make...

I have a Function that I have been using to determine what other workstations are logged into a database using the CurrentProject.Connection. It worked well until Access 2010 got pushed to my pc and now I get the subject line error message. I also had Access97 and Access2003 on my pc so the IT...

If you know the date associated with each row, you can get the information you need to tell if it is a weekend. Once you get that information you can add a column with a true or false flag (as shown below) and then use that flag as a criterion in your COUNTIFS. Assuming your first column has...

Use Windows Task Scheduler to start the program every day at a specified time and use an Autoexec Macro (or a Startup Form) to run the code to check if the due date has arrived and, if so, print the document. After printing (or if the due date has not been met) close the application.

@lameid -- Thanks. I think the only hope of figuring it out is to work it from the inside out. It hurt my head a bit, too.

Try this: SELECT [EmpName] [PosNum] [RptToPosNum] FROM tblMaster WHERE [PosNum] IN(SELECT [RptToPosNum] FROM tblMaster WHERE [RptToPosNum] Not In(SELECT [RptToPosNum] FROM tblMaster WHERE [PosNum] IN(SELECT [RptToPosNum] FROM tblMaster)) ); I think it works, but I got very confused when...

Tools, Startup, Display Form/Page

The way your DLookup is stuctured, you will get a positive match if ANY password in the table matches the password in the textbox, even if it does not belong to the current user. Effectively, you are saying 'If this password is in the table, it is correct.' While it is not likely that someone...

In the comment just before the Password DLookup you say the table is tblEmployees yet in the DLookup you have "UserInfo" where the table name should be. Which is it?

Duane's solution will work quite well. I have also used something like: Select tblAgency.Agency FROM tblAgency UNION SELECT "(None)" FROM tblAgency ORDER BY tblAgency.Agency; because some people find selecting '(None)' more intuitive than just a blank space. The '(' will cause '(None)' to sort...

Outlook is a strange bird. Your problem is not a default start time, it is the format you are using. I was baffled by this for a while myself and had built my own work around until I figured it out. The proper format for the Items.Restrict when using a date such as CreationTime or ReceivedTime...

Put the DoCmd.Close acForm, "frmMain" in the Form_Open Event of frmAdmin. Or, if you are going to return to frmMain when you close frmAdmin, just make frmMain invisible when you enter frmAdmin, and visible when you leave. Forms("frmMain").Visible = False

You call the procedure withDoCmd PrintPDF() but your procedure isFunction PrintPDF(SrcReport As String) First, do not use DoCmd to call a User-Defined Function. DoCmd is for specific Access Functions. Second, the Function you have is really a Subroutine -- Functions should return a value and...

OK... I am a bit confused (don't worry, I am used to that feeling.) In you first post you have: Now you have: And in the last post you say: but your sql statement has So are the controls called 'Country' and 'Presort' or 'Country_Select' and 'Presort_Select'? Did you change their names...

If the listbox is called 'Country' then just use [Forms]![Desp_Parameter_Form]![Country] The value of the listbox will be the selected value. Use the same logic for 'Presort.' Things get more complicated if it is a multi-select listbox, but based on what you have shown us I don't see that...

Only because people are used to seeing it (and using it) and there are ways of doing what he wants without hiding it. I don't like taking users out of their comfort zones unless there is no choice.

I should have accounted for that in my original post but I fell into the trap that ID would natually be numeric... and of course it could be text. I strongly recommend that you have a primary key that is numeric.

Oh... you mean the BIG 'X'... no, you can't hide that one (and you shouldn't.) The On_Close Event should do the trick short of pulling the plug or hitting the Power Off switch.

First, your SQL statement won't work because your syntax is wrong. It should be sql = "SELECT * FROM T_Employee WHERE UserID = " & me.User_ID That will get your value for me.User_ID in instead of the text 'me.user_ID' -- likely the source of your error. This syntax is good if User_ID is a...

Ahhh... you said 'next column' so I thought that meant the combo box had more than one column. You mean the next field in the table? Since I obviously am not familiar with Visual Studio, I will now shut up.