Search results

There was no mention of lots several requirements. If the OP didn’t state all detail lines will be the same height, it’s good practice to assume there may be growth (and then ask).

I don't believe you can create a union query with SQL like: SELECT * FROM Yourtable UNION SELECT A, B, C, D FROM Yourtable EDIT: I tried and this actually worked SELECT yourTable.* FROM yourTable UNION SELECT Null, Null, Null, Null, Null, Null,Null FROM YourTable; I also changed the name of...

A couple issues. 1) your record source is a table name with no field names. Change the record source to qselYourTable with a SQL view of SELECT YourTable.ID, YourTable.OrderNumber, YourTable.StopNumber, YourTable.CustomerName, YourTable.PONumber, YourTable.ItemNumber, YourTable.ModelNumber FROM...

Merry Christmas from MinneSnowta where we are blanketed with the white stuff.

The code worked for me as posted in #1

Have you considered a multi-select list box rather than a form?

I realize his naming choice based on my pleading for a simple example. Be careful what you ask for.

I would prefer to have my name on dialogs other than errors.

Since the BE is SQL Server, you should consider using a solution that puts the work in SQL Server like a pass-through.

The folders were created and tables relinked except I couldn't find [Selectie_tbl]. Also the database won't compile since it is missing some reference. Maybe the general.mdb needs to be configured.

I agree with the pass-through query since these are typically very efficient. There was no mention of the number of records and fields. Also, are all fields required in the reporting?

We had a similar normalized table structure at a former employer. We added an attribute table to store different characteristics about a Part. For instance the attributes common for hard drives might be manufacturer, size, type, etc. A printer would have paper size, brand, model, ink/laser, etc...

I was expecting: Persons PersonID PK FirstName LastName Address Phone Groups GroupID PK GroupName PersonGroups (Junction table) PerGrpID PK PersonID FK GroupID FK I would add to the confusion of multiple persons at the same address or multiple phones or phone types. Just the...

If this is all true then it makes sense to not post your ideas in threads where they will never result in any level of support. I assume you could contribute some minor, repeatable, implementable ideas that could help someone. I see lots of posts that move away from hard-coded designs to a more...

@Imb, if you could post a very simple demo of your system for something as basic as managing a mailing list with the ability to create groups. In a standard Access app, this would require about three tables and three forms. My best guess is your system tables would resemble the results of the...

A running sum to get the totals would probably work if you removed the BeginBalance from the longer expressions and added it back in as a single value.

I would like to give @phillip the benefit of the doubt by assuming this was a data report that was produced by an accounting system. With those kind of numbers, it's hard to believe they are all keyed into that table.

You could pitch your solution to one of the group leaders at the Access User Groups. Typically they are going to want a PowerPoint and documentation to even consider your presenting. Some group leaders will want a walk through of the presentation prior to exposing you to their members. (I...

I'm not sure why you would do this from the main form when you are displaying potentially many invoices in the subform. You could have a text box (possibly hidden) in the main form that gets the value of the current InvoiceID from the subform code. Then use the text box in an update query of the...

Everyone with less than 100 posts have some limits to what they can post. Maybe a link (even in a quoted reply) or other content.