Search results

Pretty odd! Have you checked the Menu bar's properties. It may be that when the form's min/max/restore stuff is put on the menu bar it takes on the menu's properties. GumbyD

Rowena - OK - I think I finally got it all worked out. This turned out to be much more difficult than I originally imagined. I had to add 3 queries and I updated the table and the code. I hope it all works for you! GumbyD

anewor - Sorry I had sick child issues and have not been at my computer. As for the error message - I think it may be related to the field size of the MailingName field in the the MailingLabelList table. Try changing the Field Size to 255. As for the other updates I will take a look at the...

anewor - Please see the attached database for the code. You can run the code in the immediate window by typing CreateMailingList and then pressing return after it. When you run the code it will populate a table called MailingLabelList. I put comments in the code to help you make sense of it...

I looked at your diagram and then created some tables to try an replicate your issue. When I tried to do it just using queries it became pretty bad, pretty fast. I think your best bet is to use VBA code to process the information. If you can create a query that lists all of the clients that...

OK - in your query criteria I am guessing that you have an iif statement that looks something like the following: iif(isnull(forms![YourFormName]![YourFieldName]),[Enter Date],forms![YourFormName]![YourFieldName]) If not then you need something like that to prompt only if the form value is...

You made the fatal error of trying to store these OLE objects in Access (sadly Access saves these objects as BLOBs - binary Large Objects). I have delt with this by storing the OLE objects in a seperate directory and the path in Access as a text field. When you want to display or print out the...

Brian - I think what is happening is that the code is pulling the first value for column three in your list - which I am guessing does not equal "34-15". What if you wrote the value for the field name for the "34-15" field (I am not sure what the field name for that one is) to another hidden...

Jim - You need to use a totals query to get your information. Group your records by Customer and then sum the power usage for each month. Make sure you criteria for the time period you want to sum up (Between 1/1/03 and 1/1/04 or whatever) then use the Where selection in the groupBy row...

Could you try updating the value list property in code? I am not sure if it would work, but you could create the string in code and then update the property. It might be a bit faster if you can get it to work. GumbyD

You should be able to use the format function on that field in the middle of your concatination like this: "We will be using the facility and be delivering on" & " " & Format([DeliveryDayCalc],"mmmm dd"", ""yyyy")& " " & " If ther are any questions please cal See if that works for you GumbyD

Amileaux - Because your warnings are stilled turned on Access is just processing your error message on top of it's normal messages. I think since you know what is causing the issue and since you are only added one record at a time from this form, I would just add a SQL statement to check and...

EmmaJane - Here is some code that should work for you. Please see the attached image to see how I used the code in a query. Public Function ConvertNumber(IDNum As Long) As String Dim rstConv As Recordset Dim X As Integer X = 0 Set rstConv = CurrentDb.OpenRecordset("numberconverter"...

Adam - I will just throw my 2 cents in. When you say you are going to secure the database, I am not sure if that means you are going to create your own MDW (workgroup information file) or if you are just going use the standard one (System.mdw) and add Users and object level security. I have...

Try this little function I created: Public Function WeekAssign(SDate As Date, EDate As Date, ValueDate As Date) As String If ValueDate < SDate Or ValueDate > EDate Then WeekAssign = "Out of Range" Else WeekAssign = "Week " & ((ValueDate - SDate) \ 7) + 1 End If End...

If you want it to calculate the difference in days on the report and you have the two date fields on the report, then you can just subtract the earlier date from the later date in a new text box. In a new text box go to properties > Record Source and type =[Your Later date field name]-[Your...

[DateField1]-[dateField2] GumbyD

If [WeekID] is not a numeric datatype than that may be causing your problem. It looks like you are evaluating it as a number so if it is text then you would get a datatype mismatch error. GumbyD

As long as you had already set the variable to the value and have not stopped the code exection it should show you what that variables value is in the immediate window. I may not have mentioned that you need to press the return key after you type in the ? strSQL You can use it next time...

I see this one lots of times. You are missing some data that the query needs to run. If you put a breakpoint on the code after you set your strSQL and then in the debug window type ? strSQL it will give the SQL it is trying to run. At this point stop the code exection and copy the SQL into...