Sage 100

Does anyone have access to 3.71 that has the ""distribution solution"" gl, ar, a p, so, po, im, br? I need the following file from the SOA folder: SY1Q04.SOA. It has one or more missing records and apparently it has been like this for a while (longer than the backup is kept).

try this one

Thanks Phil. Getting an error when clicking the magnifying glass in item inquiry. Looks like a missing record but not sure what it is. Any ideas?

You have a bad custom lookup/ALE. Can you remove all ALE's for that inquiry?

As soon as I click the magnifying glass the error appears. Not sure how to remove all the ales.

After looking at the Record name, I see the ###### is for the company and user codes. The error is referencing the standard lookup screen, which means there may not be another record for you to ""copy."" After copying the file, open in DFDM. Look for another record that ends with the same 6 characters (you are looking for a custom lookup record). If there is one, edit the record and change the company and/or user codes (each 3 digits) to ### - do NOT remove the existing record. You should end up with a new record named ######B00IM9, thus replacing the missing record.

Unfortunately DFDM cannot be used to modify ALE files.

Can you work on that file in another Sage instance? I have v.2016 installed currently, and know that I have done this is several other versions. Perhaps it is a limitation of v3.71.

@DougHiggs the full 3.71 install disks are on 90 Minds DropBox - https://www.dropbox.com/s/xtho758yyfhkz08/MAS90%20V%203.71.zip?dl=0

@MichelleTaylor1 When I try and use dfdm in 371 I get a record length has been exceeded or something like that. When I try and edit the file in 2016 I get the attached message.

@MoiraGoggin I appreciate the link. I have a copy of 371. This is a fresh install that was converted from 374 SQL using the Sage / DSD utility.

I could write a small program in pvx to change the record but seems like there should be an easier way to correct this.

Sorry, not sure why that is happening. Perhaps copying from a new install is the answer this time.

Thanks everyone for the help. I am gong to try a fresh install on my laptop and see if the new files work.

The issue has been resolved. I installed a copy of 3.71 on my laptop and copied sy1q01.soa, sy1q02.soa, sy1q03.soa, and sy1q04.soa to the client's live version and everything is well.