Search results

having umpteen tables to store this data is a sure sign of a faulty design, suggest you fix your design. Going with this. Store your union query as qryUnion Select union all select etc. Store this as qryTeller Select ID, SEGMENT, COUNT(*) as AantalKeer From qryUnion group by ID, SEGMENT...

No its not simple to do, not crazy difficult neither if you know how. What you want is a search form and/or a cascading combobox... have a look around and see how far you get with that come back with any and all questions you have.

no difference that you will notice. thus go for the best solution and split the columns.

docmd.transfertext is your friend both for import and export.

Thanks for resurecting a thread over 4 years old, anyways as the thread suggests, current date should not be stored at all. To compute the days you can run a simple query and calculate: DaysSinceRegistration: Date() - RegDate Or put a simular calculation in a form.

There is never a need to store information twice, unless you go into complex things like performance and/or datawarehouse issues.

something like: IIF(equipment1 <Date()+60, equipment1, null) as Forktruk Or if you are using the designer: Forktruk: IIF(equipment1 <Date()+60, equipment1, null) ??

Research a subject called "Normalization" a database works a lot different from a spreadsheet. Try to forget anything you think you know about excel and stop applying it to a database. Come back with any questions.

Spaces in filenames.... is it compiling the path properly? Otherwize try adding "" around the entire path.

Private Sub Cbodeladdress_AfterUpdate() On Error GoTo Cbodeladdress_AfterUpdate_Error If me.Cbodeladdress = "Yard" Then Me.Txtaddress = Me.Cbodeladdress.Column(1) Me.Txttown = Me.Cbodeladdress.Column(2) Me.Txtcounty = Me.Cbodeladdress.Column(3)...

what is it based on ?

Please do consider these words as well as those from @Pat Hartman ...

My bad, to much used to using Oracle or SQL Server, IIF(equipment1 <Date()+60, equipment1, null) as Equipment1 Or if you are using the designer: Equipment1: IIF(equipment1 <Date()+60, equipment1, null)

There is a difference between what you want and what you should do, going against my advice and that of @Pat Hartman, this will come back to bite your rear end. You want to solve this in a query not by storing it in your table.

what version of office are you using? Docmd.transerspreadsheet or Docmd.transfertext (into a .csv file) will export your table just fine I think

How do you mean? Access doesnt have any limits, excel now a days is 1 mio records, doubt you will hit that. So what is your exact requirement?

Plus you shouldnt be using Invoice number as a value in both tables, invoice number has a meaning in the day to day business . As such it has no business meaning anything in your database other than beeing an attribute.

the question that needs asking is WHY? You can link the subform and main form to do this for you. Or if need be apply the invoice number into the sql of the form to achieve the same. Storing search information is rarely a good thing :(

Dmax ... really? Noooo !

Might be that the semicolumn needs replacing by a comma