Search results

1. if you have the times, it is a bad idea to destroy data on a general rule of thumb 2. fine whats the question? A continuation from 1 ? 3. It should be pretty simple to enter a start date and end date, then enter a schedule and automaticaly fill the table using a do while - loop...

General rule of thumb, never duplicate logic. Even if its slightly different in the base it is the same then use one query. Using union query's too often is a sure sign of bad design, either in tables or in queries.

Yeap a simple join, except your using multiple columns to join on which isnt a problem if that is te requirement and a common one at that. Many joines join the two tables on multiple columns As for the suggestion @angelgp gave, joining on a "text" field is generaly a bad idea, as you descibe...

txtClick1 ? not a very obvious object name for a date picker :( Strongly suggest you use legable, usable names instead of these generic names, will help your maintenance down the line.

you will probably need to add something about years as well. and erm, spaces in column and table names :(

certainly no dig, maybe a reference to you fixing your post :) Also, having readable code is a personal pet peave of mine that really gets my blood boiling. I just cannot understand how people in this case post a double nested IIF without alligning it and making it readable. Readable code in 9...

me myself and I and maybe the ts certainly not your perfect readable code :)

making code readable, what a novel idea, dont forget to remove the surplus ")"

Oper1, Oper2 and worse Oper1_mol, Oper1_cal, Oper2_mol, Oper2_cal is a serious design issue Best course of action is to create an additional 1:n table to store the operators Consider doing the same for all the numbered and repeating fields in your table. IdParte is no more than a concatination...

just requoting myself, using the forms construct the data is forced into access first, then queried in access or client memory rather than in the database.

Between [Forms]![Reports]![StartDate] And [Forms]![Reports]![EndDate])) is only available at access time, thus the query will be pushed to SQL without the where resulting in a rather big recordset. Between #01/01/1998# And #16/03/2020# are hard dates that can be pushed to SQL server and the...

You can make a macro to open your table or form with the proper settings Then activate the macro from the tool bar?

why physicaly access the database? Use linked tables to access the customer table directly without actually "touching" the database.

In file > Options you can tell your database to start a specific form, even display a specific Icon if you like. Feature wasnt removed, just moved which in itself is a major headache!

What I mean with random is assuming it is distance you can make nice triangles however these triangles do not add up. B, D, E 70, 23, 4 cannot happen in distances assuming this is a real world example in i.e. km distance. ABDC may get you to C however the arrow doesnt support said route :(...

I hope these numbers are random, they dont seem to make sence. How about adding a component time as well? I can see a,b,c beeing 40 and a,c beeing 50. Time wize it should probably be reversed. Routing on distance isnt the key I think as you will always arrive at a,b,c even if b isnt needed ?

1) Name and date are reserved words in access you are ill adviced using them as column names in your tables. 2) Is there any logic to your date interval? I.e. should one always look at "yesterday" to find the previous score or should it be more "the previous entry" either yesterday or 2 weeks...

Nonsense, works with any dataset just fine even if not a table I will agree willingly there are advantages to working with a sheet formatted as a table, however 99% of all things work just fine in any sheet. Easiest way to do this is to "simply" export your data as a semi-column seperated...

why store the data in a different format than that it is entered as ? or it is viewed as? This isnt the 80's no more; just store time as time, rework to seconds in a report or whereever you need it to be seconds. What you can do is "transfer" the time to a decimal using either cdbl or...

I am having simular problems but pertaining to the Dow Jones, it is freaking all over the place !