It looks like you have actually fixed the duplicates problem. I want to highlight the cause for that condition so that others reading the post (and most important, you) will be able to recognize and avoid the error in the future. You posted this query. (I didn't include code markers because I want to use color highlights instead.)
SELECT [qryReserveFolio Query].Product, [qryReserveFolio Query].Qty, qrySalesFolio.Qty FROM [qryReserveFolio Query], qrySalesFolio;
The problem is highlighted in red. This query is perfectly legal in SQL, but you have to recognize what you are really requesting. You see, SQL is based on set theory. It will give you every possible combination of records from those two tables. In this query, you have what is called a Cartesian JOIN, and you may also see the name Permutation JOIN.
You got apparent duplication of some data because you did not constrain the selection and/or presentation of content from the two tables. You were advised to use JOIN ... ON syntax, which constrains SQL to only show you records that have some particular value in common with a field value in the other table. You will often see this concept - field from table A matching field from table B - described via a Relation. Technically, SQL still starts out preparing to give you all of the possible combinations - but it then immediately filters out the records for which the joined fields do not match, and that eliminates a lot of the "clutter" that usually comes back after a Cartesian JOIN. That will eliminate the apparent repetition.