Search results

Your welcome! ... I wish you continued success! ... As a side note with respect to: >> It appears that once the function has been conflicted with a field that it bears a grudge and will not work again << Did you change the name of the Control that the field was bound to? For example: if...

Just noticed this .. >> ... and a weekday field 'Weekday'. << You'll want to change the name of that field.

So ... where is "TeachDayDate" declared? Is it a control on the form? If so, is it possible that you have a control on the form that is in conflict with the name of one of your variables? What is the value of TempDate prior to your code getting to that line? Kinda grabbing at straws here as...

Hello ML! You mention that Machine1,2,3,4 provide you with information, they do not seem to be processes ... what are they, do they actually perform operations on a piece of wood? I am in agreement with jz in the this can take some time to flush out. I have a sample of a structure for a...

Re: got it! >> I was relieved when I thought nobody had noticed. Then I saw the thread had a second page. << ROFL!! ... I've been there many times!!! ... so I can sympathize with the scenario!

Re: got it! Oh ... >> If I really wanted to refer explicitly to a field I think I would use its full reference: Forms!formname.Form.RecordSource!fieldname << Is an invalid syntax ... I am certain you were going for this: Forms!formname.Form.Recordset!fieldname

Re: got it! >> Additionally I recall (hopefully accurately) that the dot will refer to the field in the Record Source if there is no control by the name. << Actually, a form has no idea what a field is, unless you go through the Recordset or RecordsetClone properties. An Access form object...

>> Additional coding will be required to re-calculate the hours when the user changes the start or finish times etc. << This is precisely the reason way the results of calculations should not be stored in a table. In some circumstances it becomes neccessary, but this is not one of them...

>> The above posting suggest putting it on the cmdOK button. << I would use the Form_BeforeUpdate() to actually do the validation (or call the validation). And you cmdOK button would just save the data: Private Sub cmdOK_Click() If Me.Dirty Then Me.Dirty = False End Sub When the...

You mean this one? Automating Microsoft Access with VBA ... My friend (Scott Diamond) and I wrote the Access 2007 edition to that book ... Scott was the lead, as I just wrote 4 chapters on ADO and DAO. But, I have to say that I thought the orginal that you referenced (if the link I provided...

>> What if I hit the right arrow key to add another record instead of hitting the OK button to close the form? << That's what you use the Form_BeforeUpdate() event as I indicated to do in my previous post :) ...

... In support of Bob ... a triple state check box, radio button, or what ever is un-natural to work with in an option group. Since you are storing text anyway, a combo box is your best bet for a good user experience.

I will start off completely avoiding your issue --- I will get back to it, but I would like to talk to you about dates and how they are stored. Dates are stored as an 8 Byte floating point number (same spec as Number/Double) and as such you are ALWAYS storing a Date component and a Time...

>> Odd it worked with hand written SQL though? << Well ... not really ... You can actually save your Query in its original form: SELECT [Parameters].* FROM [Parameters] WHERE [param_current] = Yes; IF you Save it in SQL View --- and never try to save from Design View. The Design Grid is...

Note ... If for some reason you can not change your table name, then you should alias the Parameters table in ALL of your Query objects and recordsources ... SELECT p.* FROM [Parameters] As p WHERE [param_current] = Yes; Or ... create a query of the Parameters table (alias it if you filter...

Definately a poor choice for a table name, I was hoping that it was just a "sample" name for posting. Changing the table name to something different will yeild success with out a doubt!

>> Happy to provide but if I cannot save the query and give it a name, how can I? << Create a new query cancel the add tables dialog, then switch to SQL View, then type out your intended SQL statement ... copy/paste and post ... but try to save it first to see if the manual creation of the...

>> Both Database1 and Database2 contain the same content. << Have you Compacted them both? -- they will both shrink. Also, in Database2.accdb the Import specs are consuming some space, those specs are not present in Database1.accdb. If you delete the Import/Export specs from Database2.accdb...

So ... now the real question ... with so much data, why not simply install SQL Server Express? Its free and can handle 4GB, and since you are already using Linked tables, your FE should not have to change too much. If anything it would become simpler since you would not need the queries to JOIN...

In A2007 ... To hide the ribbon ... DoCmd.ShowToolbar "Ribbon", acToolbarNo To show the ribbon ... DoCmd.ShowToolbar "Ribbon", acToolbarYes In A97 through A2003 ... To hide the menu bar ... DoCmd.ShowToolbar "Menu Bar", acToolbarNo To show the menu bar ... DoCmd.ShowToolbar "Menu Bar"...