Search results

Ah, so I could split it, then create table on local FE then distribute? It's not 'live' yet so that's still something I could do... And no - it will be completely locked down so they won't have any way to delete the table. I'll do that instead!

OK, tracking and makes sense. We're talking in the realms of 10s and 100s in terms of order of magnitude and relatively infrequently, it sounds like a separate db is perhaps a step too far. Yes, table is likely to be re-used. Just so I get this right...: 1. Create table (TblTempSelections)...

Ok, that makes sense. Yes, database will be split. In terms of best practice, would you create the table when the form opens, (using a make table query), apply selections, and then delete table on form close? (I’m assuming that when the database is split, a “make table” query creates the table...

Hi all, My first (and almost certainly last! :ROFLMAO:) database will soon be going 'live' where I work after many weeks (/months) of trial, error and pain... The database tracks personnel, equipment and training data for my organisation. One of my forms allows a user to select multiple...

Ok, good to know it's not just me. I'm completely pixel-peeping but it's definitely still visible even using hairline! I guess it's just a bit of OCD that's really bugging me ... why is that behaviour not the same across the different controls?!

Interestingly seems to only affect list boxes. Attached example - controls are labelled. Left is ListBox. Can't replicate the issue with text boxes or a rectangle shape.

Interesting. I've attached an extreme example with the database - fancy checking to see if you get the same issue?

Can be set to transparent but then that defeats the point... I suppose I could use a rectangle around each list box to overlay a border but seems like a faff.

No, there doesn't appear to be a 'Back Style' property for the listbox. Only 'Back Colour' ...

Hi all, I've just noticed something which has really started to bug me; it seems access creates a very thin transparent border on the inside of list boxes used on a form. When the border is small, it's not really noticeable but no I've noticed it I can't unsee it! I've attached a sample image...

Well... one step forward and two steps back...! I remembered the reason why I wanted to specify the column names... I need all the columns displayed whether they have a value in or not. Using your method sorts the columns but still the only data that's displayed are the ones with a value. I...

@arnelgp - thank you, I managed to get this working with an APPEND Query to add the sorted field / column names to the sort table.

Thanks all, very helpful. @Pat Hartman we have one "line manager" and then several individuals above in the heirachy that have a reporting function on the individual - which may or may not include their line manager (simple! :) ) After some thinking - it's almost a moot point as the case for...

Interesting. For this particular application there's no requirement to keep the record of anyone who has left so it would seem "cleaner" to me to just delete the record. Thoughts?

I did put them in a child table to begin with and used a subform to display it on my main form; it slowed down the form quite a bit so I reverted to having the fields listed in the main table.

It's probably my lack of understanding - I did not want to clear the whole field. In the above example, Jack leaves the company and his PersonID is deleted. Presently, with the defined relationships, it deletes ALL staff members who had him as their top level supervisor, rather than delete his...

Hi All! This is probably really simple - but I feel like I've got a fundamental misunderstanding of how this is meant to work. I have a table with several fields; three of which are "supervisor" fields. Issue: When I try to delete a member of staff, ALL related records are deleted, rather...

Attached example to show what I mean - you'll see the other row headings as an example; these would need to be displayed in the sorted xtab.

@arnelgp sorry that's not what I meant. There are ~10 fields that are defined as the "row headings" in the original crosstab. These are required in the sorted crosstab as this gets exported to excel to use by another department. When the new SELECT query (the sorted crosstab) is generated -...

@arnelgp - that looks absolutely spot on. Hopefully an easy fix - the new query that is created does not have the previous cross tab fields in by default (they appear and you can add them in qry editor and it works great). How would I get these fields in the new sorted query (they are things...