Search results

This is clearly wrong. In a typical Excel table itself there are no column-related uniform data types - in an "intelligent table" as a later imitation of a database table in preparation for Power Query (internally a modification of SQL Server) there are. With access via SQL /...

This has little to do with real databases; I would classify it as experimental programming. But technically that's not a big challenge either. 1) Bring the records from the three tables together => UNION query 2) Use it to create a crosstab query 3) Using a maketable query, you create a new...

If you have mastered everything (which I doubt), you need to train and apply your knowledge in practice. A good tool is a forum where you will encounter many questions and challenges. You can answer these questions using your own resources and solve the challenges. Ideally, you are smarter, more...

Use a select query. SELECT * FROM ChildTable WHERE ParentID = YourProductID

I haven't had a case for this yet. But you have to program cleanly and completely. MS Word is a little more critical. I know the statement of a Word expert who instantiates a new, self-created Word instance in its own class in order to then dispose of this instance cleanly and completely.

To edit several records at the same time, you will need to use an action query. As Pat correctly states, an update query destroys historical data. Under German tax law, relevant data must be retained for at least 10 years. But the school itself will also have its own historical development...

You might think Excel would be difficult. https://www.access-programmers.co.uk/forums/threads/closing-excel-from-access-vba.331172/#post-1920734 If you don't read, you can guess a lot. Code in #46: With Selection With xl.Selection Selection is an Application object and so must 1) at all and 2)...

sSQL = "SELECT * FROM QueryX WHERE " & Me.Filter Instead of * you would of course only list required columns.

Since I won't repeat myself, you should repeat working through the answers.

Content: You're just deleting it. Maybe you should export a planned query instead of some collapsed entity.

Dim xl As Object Dim WB As Excel.Workbook Dim WS As Excel.Worksheet This is stylistically inaccurate. Are you using early binding or late binding? This is typical for improper referencing of objects. If you run this code in Excel, it will probably work better because Excel knows itself and its...

Yes, same is same, and similar is similar. Don't be afraid of lots of records, that's what SQL is for and how to use it well. Of course, such duplications would not be recorded; one connection is sufficient. But the statement alone is certainly similar and therefore a classification is not...

With Power Query (Excel) you can read a lot of data sources and then revise them. So you could create a usable table and then add it to your database.

If ProductA is similar to ProductB and ProductB is similar to ProductC, then ProductA must also be similar to ProductC. This third pairing must also be reflected in the junction table, and then you will always find all products that have been explained and defined similarly to one.

Since this will probably take longer, I have written down my thoughts in the attached demo. It will be shown: 1) how I imagine a useful may-to-many relationship, 2) how to UNPIVOT the original table, 3) how the data in the resulting list is divided into the tables of the relationship, including...

SELECT P1.ProductName AS Product1, P2.ProductName AS Product2, P1.Size - P2.Size AS Diff FROM tblProducts AS P1, tblProducts AS P2 WHERE P1.ID < P2.ID ORDER BY Abs(P1.Size - P2.Size) Here, similarity to a number was interpreted as size.

A real example should be based on a real database. So upload an example database with some representative records here, including the existing indexes and relationships.

Is the table an export/import or a direct link to SAP? Furthermore, if you have a view, a query or a report in front of you, it also looks like a table. As well as: Not only developer gods work in SAP. Great software and software names do not guarantee outstanding performance. This table is a...

Then you can forget about a reasonable query. SQL works row-oriented, not column-oriented. But with VBA and the appropriate skills you can solve everything, even if it is more complicated and time-consuming. With such an Excel-typical structure, you can also switch to Excel for processing. But...

Your table does not correspond to the expected table design for a database. http://www.allenbrowne.com/casu-23.html The first correct step should be to break down this table into a many-to-many relationship. This cannot be used in a useful way. In the table for frequencies there should be a...