The first one is NEVER use a combination of linked tables with local tables in your queries.Instead download the server side tables as temp tables in your app or upsize your local tables to SQL Server and do the processing on the server in it’s entirety.This walk-through outlines the process of creating an Access form.Start Microsoft Access and open the database that will house your new form.The new form will allow the entry of new runs and modification of existing runs.Before you begin the form creation process, select the table that you want to base the form upon.The preferred method would be to perform the calculaiton (probably in a query) whenever the values are needed.
This example builds a form based upon the Runs table.It's therefore not straightforward to have a form textbox that is simultaneously showing the table value and a value calculated from other sources. you could update your table manually using the recordset object like so...rs as dao.recordsetdim dao.recordsetset db = currentdbset rs = db.openrecordset("SELECT * FROM tablename;", dbopendynaset)rs.findfirst = "somefield = " & uniquevaluewith rs ! calculatedvalue2 = i Calculated Value2 .updateend withmight be a bit cumbersome but it should ensure that the values get entered properly.The findfirst is just basically a lookup using a unique value from the form for the record so you ensure you are entering the values into the proper record. if the box is checked, it adds 45 days to another field and enters this date in the form. I understand now that it is not advisable to save calculated fields to a table... therefore, when I run a report based on that date.... Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.The table basically has all the above fields and i wanted all the calculated values to show as well as the other data. by the sounds of it, it probably would be simpler to store the estimated revenues then create queries using the stored numbers, if it was just for viewing purposes on the form, or on a report, a calculation would be fine, but it would get reasonably convoluded if you were wanting to use the calculated values for other calculations/queries.Then i would create querys based on different needs but always being able to view my monthly estimated revenue. Well you can try the method I've described above for storing you values, again, cumbersome but it'll work. I, personally, would never store calculated data in my tables unless it was needed for historical purposes.Although Access 2013 provides a convenient spreadsheet-style datasheet view for entering data, it isn’t always an appropriate tool for every data entry situation.If you’re working with users you don’t want to expose to the inner workings of Access, you may choose to use Access forms to create a user-friendly experience.hope I'm making sense, lemme know if this helps at all... Basically..database I created is being used to track jobs that we process on a daily basis as well as estimated revenue.randy700's point is well taken, if the values are derived from values already present in the table, and you already have all the calculations coded in you could just calculate the values everytime you changed records on the form, that would reduce the number of fields you'd need in your table.... It includes a specific month code, customer name, total units, permit cost, stamp cost, and meter charges (permit, stamp & meter, become calculated on the form into a field labeled "combinded postage amount, then I have fields for sales reps, commission, invoice #, invoice amount, and estimated revenue ( calculation based on invoice amount - commission - combined postage, this give me my estimated revenue for each job.)Then i wanted to create a query that took the specific month code, added all the estimated revenue values to give me a grand total for that month.