Search results

Worth checking, in the underlying data Table, exactly how the Date is being formatted and stored. Other than than, try Conditional Formatting of the Field in the Report, rather than Code?

Sounds like you have two subforms displaying the same data, whereas you want to see all sequential records ... in which case you don't need subforms just a main 'continuous' form with stacked data as in your current setup.

You might need to tell us a little more ... You can have a Main form with multiple linked subforms and the data displayed in the subforms should be controlled by the record selection made in the Main form using Master and Child links in the subforms. Are your subforms set up in this way? ...

Not sure why you need to create a Command Button to open a Data Entry form ... and I strongly suspect this is where the disconnect is arising. If you have the Main and Subform linked then you should be able to add Notes in the subform to any record displayed/selected in the Main form. Just...

Rather than "0:00" which won't ever be recognised as a Time format, try "00:00:00" or "00:00" (depending on the exact format for the field)

You need a TABLE to store Prices and Price Change Date Points Fields:Card; Price, Effective Date e.g. Birthday; £0.75; 01/02/2012 Birthday; £0.80; 15/02/2013 etc Then build a SUM Query using the MAX 'Total' function on Effective Date to get a current price list for all Cards. Use the MIN...

You should be looking up from a separate table or query?? Check that you are doing this first.

13GB is really not a big database ... I have databases running 200GB+ incorporating 10's of thousands of data records in multiple tables. In what way is your 13GB database underperforming? For now, stick with Access unless you have a budget to burn!

You should be able to copy and use the same Total fields in the TYPE footer ps: rather than SUM([Field]) you should be using the expression COUNT([Field]) as these appear to be non-numeric fields you are summing? Maybe this is part of your problem?

Sounds like you need to change your Query from a SELECT Query (which will display all records, including duplicates) to a SUM Query (where you can customise grouping levels)

Hi Hi Leslie There's a widely accepted wisdom that says you shouldn't ever put calculated fields into a table ... rather you should always use a Query to calculate the value when it's required and then paste the result into the table. In this instance it sounds like you should run a Query...

Yes, starting from scratch and building up gradually you'll need:- Calendar table with the following Fields Holiday Year; Quarter; Month; Week; Date Employees table:- Employee ID; Name; Std Daily Hours; etc Holidays Booked table (this is where the holidays are stored):- Date...

Update: I moved the database from a Windows XP/Access 2003/2GB Memory workstation to a Windows 7/Access 2007/4GB laptop over the weekend and the 'flicker' has disappeared! Not sure which element of the laptop configuration has cured the 'flicker', but happy enough that it's gone.

Yes, I read that dialogue and it's a little above my head! It sounds like many roads lead to Rome on this one!

You guys might of course be right re "heavy" ... but I am trying to achieve a one-stop User Interface screen and whilst the 'flicker' is both noticeable and annoying (to me at leat) it fortunately doesn't appear to affect the response speed when selections are changed.

Start out simple ... Three Tables: 1) Consultants: ID; Name 2) Qualifications Desired: Professional Body; Qualification Description 3) Qualifications Attained: ID; Qualification; Date Attained Start out by populating these tables the way you're most comfortable with i.e. Manually or via...

Right now the Database is in its development stage and not yet split. I will split the database closer to the deployment phase of the project. When deployed it will simply run as an A2007 database.

I have copied the following code (found in another thread on this forum http://www.access-programmers.co.uk/forums/showthread.php?t=221559) into a new Module Public Function getWinUser() As String getWinUser = Environ("UserName") End Function Then, when I need to call on this ID in a Query I...

The flicker is always there ... evn after a prolonged period of inactivity on the Form.

Hi Alan is your's an A2007 database?