Search results

Storing calculations in a table shouldn't be done. The milestones you want to find can be calculated in a query based off of the sales date. No appending necessary. 180DayMark: SalesDate + 180 30DayMark: SalesDate + 30 10DayMark: SalesDate + 10 Any comparison can be done that way.

You want to make sure that the database is split up into a front end (Has the forms, queries, reports) and a back end (Stores the tables). You link the tables from the back end to the front end. You also want to make sure that EACH user has their OWN copy of the front end on their local drive...

You can link the csv file as if it were a table. (Not sure if you can edit it...never linked a csv file). Go to File-->Get External Data-->Link Tables Follow the Wizard

I've started to play around with Sql Server...and found this function (I believe on MS website) Function CreateSPT(SPTQueryName As String, SQLString As String) On Error Resume Next '----------------------------------------------- ' FUNCTION: CreateSPT() ' PURPOSE: '...

I'm a bit confused why you are using a dlookup for every field. What you are looking to do can be accomplished with a combo box. There is a NotInList event for a combo box. You can use that event to add the new account number. dlookups are slower than a query and should be used sparingly. As...

Yes, the code would go on the On Change event of the first combo box. You would requery the second combo box. Make sure you are putting the code in the code builder and not just the field for the On Change Property. (Click on the Properties, then the Event, then the button with the 3 dots on...

To repopulate a combo box, you need to do a .requery Would look like this (Put on either the On Change or After Update event of the combo box): me.ComboBoxName.requery That should do it

Another factor that comes into play when it comes to help is the perception of yourself that you put out there. The way you act plays a big part on not this forum, but forums in general. Genesis, you make reference to your post about proper syntax for an Insert query. You say that it hasn't...

Open up the VBA editor (in Acess2003: Alt + F11). Click on the help button and search for DateDiff().

If CallDateTime is stored as both the date and time, then when you use a short date it will tack on 00:00:01 as the default time so it can compare the values correctly. Either add 1 to the end date criteria, or add in 12:59:59 PM to it.

Give them a few good slaps for that :)

Well, if table setup were correctly normalized, it wouldn't be a problem :) What you should of had (have) is one table for the Donor and their information and another table where you record each donation (Including the DonorID and the Donation Date). But since you dont, you are going to have...

Yup, it's what is called Cascading Combo Boxes. Basically, you use the choice from one combo box as criteria for the next one. So, in your case, you could do something like this: First Combo Box: Select * from tblCountry Second Combo Box: Select * from tblStore WHERE countryID =...

You can establish a relationship as many times as you want. Access doesn't care :) You shouldn't need to re-store the Country and State if of the store if that information is stored in the tblStores. You can populate some unbound text boxes to show the data if you want. You should only store...

Without knowing the table structure, I dont think I can be much help. The only suggestion is that if the design grid doesn't have enough lines, you are going to have to manually write the Sql. Personally, as much as may be a pain, I would redesign it. I dont know what time contstraints you are...

Glad it worked out!

To impliment the code, you need to create a module with the code provided on the page. You would substitue this line: strName = "H:\Dir\Backend1.mdb" With the path to your backend database. The code provides for serveral backends. If so, just replace the directory of each backend. If it's...

having 150 fields in one table screams of a design flaw. Read up on Normalization.

Each person should have a local copy of the front end on their own computer. If they both are using the same front end over the network, that could explain the slow down. Having two ppl use the same front end could also lead to corruption. Plus, the advantage of each person having their own copy...

If you want to tally up the Number of instances, then you want the count, not the sum. So the query should look like this: Group By: Dlr_Num Count of: New_Acct Count of: Disconnect Count of: Dlr_Access Count of: Transfer Where: Entry_D