Date doesn't update

[aaronburro]

The date for my MAS client never updates. I have to set it every stinking day. No one else in my company has to, however... What do I need to do to fix this?

 

[aaronburro]

after a little bit of research, I have concluded that the option I need to set is allegedly in "File|Preferences." Only, "File|Preferences" doesn't exist. Furthermore, the other place where I should be able to fix this is currently set to auto-update the date every session as well :/ what now?

 

[aaronburro]

any ideas?

 

[GingerPeachy]

You must be on 4.0 or higher, since you do not have File/Preferences. You need to go to Library Master/Main/Company Maintenance/Preferences.

 

[aaronburro]

Well, I checked to be sure that the appropriate box was checked, and it is. It seems to only happen to certain users, while every one else is just fine.

For reference, when I log onto MAS200, the accounting date is shown as the current date, but as soon as I choose any modules the date changes...

thx in advance

 

[aaronburro]

Just to let the forum know, this seems to be a common problem in MAS200. I "found" two solutions, and I'll detail them here:

OOOOOOOOOOOOOOOH this problem makes my TEETH ITCH! It had only been occurring to me for a few months and to no one else. I mentioned it to my boss the other day and she said she had never had any trouble like that. Then she comes up to me two days ago and says she started having the same trouble. We use MAS 200 4.0, so the manuals are all outdated on how to address this little quandry. If you go to LibraryMaster|Main|ModuleDateMaintenance, you will see what the currently logged on user's dates are set to for each applicable module. If the user has NEVER tried to change the date for any modules, then this window should be empty. However, if the user HAS changed any accounting dates, then whatever module he changed will show up in that ModuleDateMaintenance window. If you click the printer icon on this window, you get a report showing every who would have anything in that window.

Long and the short of it? I think this is a bug in the software for at least version 4.0 (cause thats what we use) that isn't pulling the accounting date for each module from the LibraryMaster date. That date DOES update to the system date if you have that aforementioned box checked in the Company Profile | Preferences tab.

Now, how to fix it? Well, I haven't exactly figured that part out 100% yet. I've found one way which addresses it, but it is FAR from elegant. Basically, what you do is you set the affected user's affected company to prompt for the accounting date. Save the company profile. Then have each affected user go log into the company and IMMEDIATELY log out. Then the supervisor goes back in and unchecks "prompt for accounting date" and RECHECKS "auto set accounting date." The affected users should then be golden again, as long as they don't change the accounting date. In addition, if you have multiple companies in your MAS200 system, you will have to do this for EACH company that any user has a problem in. Pain in the rump, if you ask me.
EDIT: I tried this method yesterday and it worked 100%. Still, its a pain in the butt

The second way that I *think* will work, is to go into the Data File Maintenance Utility and open up the SY_ModuleDate file which is in the MAS_SYSTEM folder in your MAS90 server directory and delete each entry that corresponds to a specific user. I *think* the first two records should be there, so I wouldn't delete those. Basically, if you try this route, after backing up the SY_ModuleDate file, print out the contents of that file from the data maintenance utility and then print out the aforementioned report from the ModuleDateMaintenance window, in addition to the SY_Users file data from the Data File Maintenance Utility. You can then match up each record in the SY_ModuleDate file with the appropriate users and "be sure" you want that record gone. If you do, then you just navigate to that record and chose "Delete." Like I said, though, back up your SY_ModuleDate file before you do this. I have not personally done this, but it stands to reason that this is the file that is involved w/ this particular problem.

Hope this helps!

and as an addendum:

I can officially confirm that deleting the extra records in ModuleDate works. I did it myself Thursday the 7th, and it worked flawlessly. My only reminder, though, is to BACK UP YOUR MODULEDATE FILE! It is extremely easy to delete the wrong record with the Data File Maintenance Utility because after you delete a record, it goes to the beginning of the record file. And guess where your default, AKA VERY IMPORTANT, records are in that table? at the front. So, delete them from the back so you can be SURE you don't delete the default records, if you try this

BTW, if you have to replace your ModuleDate table with your backup because you goofed and deleted something you didn't want to, you'll have to shut down the MAS server before you can replace that particular table