This usually indicates that the workstation has lost connection to the network

End task out and attempt to access the manex system again. 

Information on Creating New Views in ManEx Data.

If the user is using Crystal Report or another third party report creator they can create what ever they need using that software.  If however the user wants to create a view using VFP in the ManEx DBC, then they will have a problem because everytime new DBC's are released the new DBC's will remove their view. 

Another solution would be to create a completely new DBC container and use ManEx tables to create views that the user needs.  Make sure that the views are not updatable (this is very important) and be sure to name them with some kind of prefix to avoid confusion with the same name in the manEx DBC's.  Then if ManEx changes the structure the user would have to manually update their views.

MANEX does not have a Cut function but it does have Copy and Paste functions in the larger free-form fields like the Notes and Profile fields.

Copy and Paste instructions are the same as in most Windows applications:

a.      You must be in a field that is active for Copy and paste.

b.      MANEX must be in Edit or Data Entry mode for Copy and Paste to be active.

c.      The cursor must be active in an editable text field.  Tab or mouse click to get there.

d.      If you are unsure if Copy and paste are active, click on the MANEX Utility pull down menu.  If both are grayed out, then the function is not active for that particular instance.  If only Paste is active, it means that the Copy command has already been activated and Windows is ready to Paste.  Copy may be activated again by painting the text you want to copy and hitting “ctrl + c”.

e.      To Paste, go to the designation, place the cursor at the place you want to paste and hit “ctrl + v”.  You can also left mouse Click Copy or paste using the MANEX pull down “Utility” instead of hitting the “ctrl + c” or “ctrl + v’.

1. The best way to report an issue is to submit a KB (Knowledge Base) ticket.  This way the entire support group will receive the ticket for review.   For further detail see How do I submit a Ticket?
2. You can e-mail the issue to support@manex.com and the entire support group will receive the e-mail for review.
3. If it is an an emergency and you need to contact Customer Support immediately you can call the Customer Support line

Q.  How do I track SETUP and RUN Times for Capacity Planning, Job Costing or Product Data management in MANEX?

A.  There are TWO different ways to track SETUP and RUN times for Capacity Planning, Job Costing or Product Data Management in MANEX.

• By entering Run and Setup Times in the Work Order Traveler Setup  module
• By entering the Run and Setup Times in the  Production Work Centers & Activities  module

Using Run and Setup Times from the Work Order Traveler Setup module is preferred when there is great variability in the products produced and the setup and run rates in each Work Center.

Using the Run and Setup Times from the Production Work Centers & Activities module is preferred when the product flow is uniform, the machine rates are well established and the setup times are very uniform regardless of product.

Use of Run and Setup Times is optional unless either Job Costing or Capacity Planning Modules are in use.

The MANEX System directory is usually named MANEX, and resides just below the root directory as mapped to the server from the work station.   For some people, the name is changed for internal reasons.   For example, a user may have a copy being used as a test database, to be used for training and testing.   This database directory could be named MANEXTRAIN, or MANEXTEST or MNXTST, but NOT "MANEX  TEST", with a space in the name. In the Visual FoxPro, references to directories and subdirectories must be contiguous letters.

“MM/DD/YYYY Automatic Reindex could not be run.”

Possible Reason #1:

1. Programs for creating a backup
2. Common frequencies to create a backup
3. Potential issues from creating a backup
4. One possible process for creating a system backup

This is far from comprehensive, but should provide a good start to help you selecting the setup that will work best for you.

My Novell Server says it won't support long file names.   How do I run Update?

First, create a temporary directory on a local drive with at least 100MB of free diskspace greater than the size of the MANEX System subdirectory on the server. Name this directory "MANEXTMP". Then copy all files and subdirectories from the "MANEX" directory on the server to the local drive in this subdirectory (MANEXTMP).

Follow the procedures for updating, except when the program asks for the MANEX System directory, select the local directory C:\MANEXTMP. The program should run without a problem.

After the update has completed, then copy ALL files and subdirectories from the C:\MANEXTMP back to the MANEX System directory on the server.  After verifying that the update was successful and that MANEX is working properly on the server, then DELETE the MANEXTMP directory and all files and subdirectories below it.

For experienced MIS personnel who are CNE's the Novell site:

    http://developer.novell.com/research/appnotes/1996/november/02/02.htm

may be referred to for further information on downloading long file names.

• Check the Speed of the CPU on the work station, the amount of memory, the amount of free hard disk space and the fragmentation.  These things can make a HUGE difference when accessing large data sets.  This is not a MANEX issue per se but one involving the windows environment in general.
• Check for other applications running in the background on the work station such as a maintenance program, multiple applications, TSR's, ISP (This would conflict with the push down on-time service), Screen Saver (If the screen saver is running in the server, this can take up to 90% of the server resource while running and intermittently slow down the system).
• Check the access time on the work station hard drive
• Check the number of records in the files being accessed
• Check the complexity of the the query (that is how many "filters" used to limit the records to be returned)
• Check the number of records to be returned
• Check to see if the wires are crossed.  Basically, what happens when a computer sends out a message that it has not received, then data will be re-sent.  This causes extra network traffic.  So the error messages are multiplied.  Fluke has a test that will test the wire mapping end-to-end.
  

• Check the speed of the network
• Check the distance between the work station and the server
• Check the number nodes and routers on the network between the server and the workstation
• Check the access time on the server hard disk
• Check the number of users on the network
• Check the number of users accessing the same files
• Check to be sure that there are no system monitoring features running on your workstation or server  (make sure that your Virus Scan or Monitoring system ignore (do not scan) any executables located within the ManEx root directory. Some virus protection schemes check every access to a file, and will greatly bog down MANEX
• Is your installation using UNCS to point to the installation location on the server?  While this will work in most circumstances, the recommended procedure is to assign a drive letter and reference the drive letter in the shortcuts to the application
• Within the shortcut to any of the MANEX executables, there are two fields:  The first, “Application”, should point to the executable using the assigned drive letter as above.  The second field, “Start In”, should point to a local drive resource temp file location, such as WINDOWS\TEMP.  Temporary query results and certain system set up files are created on the fly when MANEX is run and the danger is (if one uses a shared resource for the temporary files) that the file names will collide with each other causing a system error
• On your network protocols, are you using TCP/IP or NetBEUI?  If possible, restrict to TCP/IP.  Check to see that the server and the workstations are configured the same and there are not any conflicts with addresses of cards or workstation names.
• Check the server records to check on collisions and bad packets.  If high, the hub may be a problem. 
• Make sure there are not resource conflicts on the server.  Is MANEX the only product running on the server?  If you are running your modem or Internet connection on this same server, you may be timing out if the server is busy doing something else.  Serial communications in particular take a lot of resources.  Also, on the server, eliminate any screen savers and turn the monitor off when not in use
•  If the screen saver is running in the server, this can take up to 90% of the server resource while running and intermittently slow down the system
• In the NT server, every time a user does a transaction, all of the sessions accumulate.  It doesn’t release log-ons and offs, but instead creates a new session.  The user needs to manually delete these sessions once a week or several times a week depending on the usage. (this one we would have to confirm with someone if ths is still true)  

• Check the CPU speed of the server
• Check the amount of memory on the server
• Check the amount of free space on the server hard disk
• Check the amount of fragmentation on the server hard disk
  

A: Some users have experienced the following error message when trying to run the SYSSETUP.exe and ACCTSETUP.exe through a mapped drive using Windows Vista or Windows 7.

 

 

 

 

This is a Windows error that is associated with the User Account Control(UAC) security and not a ManEx error. Because these two executables have the word "SETUP" in them it is believed to be the reason why they are flagged by the User Account Control security. 

Resolution:  The only known solution at this time is to turn down or turn off User Account Control security levels on that particular machine. This option is found under the Control panel/user accounts in Windows Vista or Windows 7.

Q.   Will ManEx run in a Virtual Server Environment? 

Q.  When should the Error Log file be deleted?

A.  The Error Log is key to keeping the MANEX system tuned up. The administrator should frequently check the error log to see if users are being dumped from the system. Copies of the errors should be emailed to MANEX at cs@manex.com to verify the cause of the error and take appropriate action. It is most useful when the user includes a brief description of the action(s) being undertaken when the crash occurred. Error logs older than the last system update are no longer required. Under most circumstances, it is only necessary to keep the last two weeks of error logs, just in case a review is needed.

Q.  What does the error message "Database Object is being used by Someone Else" mean?

A.  This error log indicates that the work station has not been properly setup. First, all users should be accessing MANEX through a desktop icon. Users who access MANEX by clicking on explorer icons will lock up system records, making others crash their data.  The PROPERTIES of the shortcut icon must show the Target pointing to the server MANEX System directory. This is usually identified as  " F:\MANEX\MANEX.EXE". 

The Start In: must be pointing to a temporary directory on the workstation local drive. This is usually identified as "C:\WINDOWS\TEMP" for Windows 95 workstations. It may be any designated directory on the Local Workstation Drive.

We are getting a system error that the error message says "File Access Denied"

This may be a work station setup problem. Check the MANEX icon on the desktop, as illustrated below:

 

About the middle of the display there is a line that says "Start In:" This line should always point to the workstation’s local drive, and a directory on it. For Windows 95 systems, it is usually "C:\WINDOWS\TEMP" but could be any local subdirectory on the workstation (NOT the server).

This message also may happen when an outside software program is used to open exclusively MANEX data with an ODBC connection. This may occur with using FoxPro, or some report writers like Crystal Reports.

Another possibility is that the user may not have network rights to the network directory.

Q.  Why am I unable to E-mail PDF files from the Manex System?

A.  Try changing the SMTP Mail Server address to the IP address. See example below: 

E-mail Set up Screen

Change SMTP Mail Server address to IP address

In order for the Export to XL to work properly Excel has to be installed on the machine that the user is working on.  If the user is using a terminal server or is actually working from a server machine for the client site then EXCEL has to be installed on the server, also.

Older versions of Excel will work but has less record space.  It is recommended to use the most recent version of Excel with Manex exports.

All exported excel files from ManEx will be formated to a text file. 

With 8.1 we had added some new enhancements to the EXCEL export capabilities of Manex.

• Within 8.1 we now have the capability to export multiple worksheets to xls format which allows us the ability to provide more detailed information within the export.
• We have extended the number of records that can be export from Manex to XLS format
• Memo fields can now also be exported to XLS

Additional reason why we had to convert to character instead of numeric format:

• XLS was automatically removing leading zeros
• If users have numbers in the system for example 10E32058, upon export to XLS it would see this character as a Scientific notation and then the information would become unreadable by the users.
• The safest way for Manex to export to XLS without causing any issues was to convert all data to txt format.

After exporting to XLS users can easily convert any of the fields to formats of their choice.If users happen to have Macros that use the XLS exports, it would be suggested to make the changes within their Macro to accommodate for the character format.

The Manex FTP site is designed to insure that no one but Manex and each specific user can access the information loaded in their FTP folder.  We can increase our allowable file size, and will do so if the situation warrants.  But more often than not, our Users ftp connection will time out before a very large file can get loaded, so we suggest parsing the file into smaller portions.

Q.  Does Manex Support Linux Server environment (operation system)?

A.  No Manex does not support Linux Server environment (operating system).  If you decide to use the Manex System with the Linux Server operating system then we can not support any issues that might stem from that.

What kind of image files can be used in MANEX pictures?

The following files types can be utilized as images in MANEX:

Q.   I installed FoxPro 9 Pro, then SP2.   Now when I run Manex, it checks the local directory and time, then the FoxPro crashes and ManEx will not open.

A.     Manex supports VFP9 SP1 only at this time.   You will need to un-install VFP9 and install VFP9 again with SP1 only not SP2.  SP2 has some bugs that might affect Manex and we will not be implementing it until we make sure that Manex is safe to use SP2. 

NT 4.0 is becoming a pretty old version and has been known for various different issues.  But upon updating our system to VFP 9.0 (ManEx 8.5 or higher) we found that our system would not function on NT4.0 servers.  Upon investigation we found a German patch that resolves that issue.

Solution:

To patch the Manex 8.5 client on NT4:

1. Copy the patch file (vfp9nt4patch.exe) to the Winnt/system32 folder & run.
2. Answer "Ja" to the popup box.
3. It will patch the vfp9r.dll file to remove long filename support.
4. More info is available by following the enclosed url...
5. It will create a backup copy of the original dll with a .001 extension.
6. It will display a dialog box when finished.
7. Manex should run ok now.

FOXUSER files are files that our application uses to save some default information, printer information, etc. . .

Q:  What are Silent Client files?  And where are the located?

A:  You will find all the information on the Silient Client files in Article #3072 .

Using VBScripting to kill the trigger timer

The following function will kill any active trigger on the local computer

 to restart the trigger create a bat file scheduled in the task scheduler to start the trigger timer back up

The task scheduler will ask you what credentials you want the task to run under and if you want to run if logged off.  If you enter the Administrator credentials and allow to run if logged off.  Schedule it to run at system start up every time the computer reboots it wall automatically start the trigger timer running under the Administrator's credentials.  Multiple scheduled times are used one to start at startup and one to start it at 4:00AM every day.

The following script will actually copy the dbfs files without the need to kill the trigger.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

'This script will copy the Manex database files with out the need of killing the trigger timer

'--------------------------------------------------------------------------------------------------------------------------------

Set WshShell = CreateObject("WScript.Shell")
Set FSO = WScript.CreateObject("Scripting.FileSystemObject")

'This is the folder where you want to copy the files to

foldername = "\\server-2003\manex_server_backups\dbfs"
if FSO.folderexists(foldername) then FSO.deletefolder(foldername)
call FSO.CreateFolder(foldername)
foldername = foldername & "\"

strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
 & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colFiles = objWMIService.ExecQuery _
 ("SELECT * FROM CIM_DataFile WHERE Path = '\\ManEx\\dbfs\\'")
For Each objFile in colFiles
  if objFile.Name = "c:\manex\dbfs\trigrun.dbf" then wscript.sleep 10 else call FSO.copyfile(objfile.name, foldername)
Next

function getDate()
'--------------------------------------------------------
  'get date and format it to yymmdd_hhHmmM
  DateTime =  now()
  YearTime = year(DateTime) - 2000
  if YearTime < 0 then YearTime = YearTime + 100
  if len(YearTime) = 1 then YearTime = "0" & YearTime
  monthTime = month(DateTime)
  if len(MonthTime) = 1 then monthTime = "0" & monthTime
  DayTime = day(DateTime)
  if len(DayTime) = 1 then DayTime = "0" & DayTime
  hourTime = hour(DateTime)
  if len(hourTime) = 1 then hourTime = "0" & hourTime
  minTime = Minute(DateTime) 
  if len(minTime) = 1 then minTime = "0" & minTime
  getDate = yearTime & monthTime & dayTime & "_" & hourTime & "h" & minTime & "m"
'--------------------------------------------------------
end Function

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Q.  Why isn't the TrigTimer being displayed on the Server?

A.  If the TrigTimer is no longer appearing in the toolbar at the bottom of the screen on the server, this would indicate that the TrigTimer has been started on one of the end user machines.  They must have logged into Manex before you had a chance to be the 1st one to log back in from the Server. 

First you can start another TrigTimer on the server by double-clicking on the <<TrigTimer.exe>> located within the Manex Root Directory.  This will ensure that a new trigtimer will not be accidently started on another pc once you stop the trigger on end workstation.  Or, you can let all users know not to access the system during this time so you get a chance to get the TrigTimer loaded onto the Server.

You can check the processes on the server to see who is running the trigtimer.exe (or go to each workstation and check for the trigtimer in the toolbar), once you find it you can stop it on that machine.  And verify that the Server is the only machine running the TrigTimer.

While in MANEX, with the desired screen displayed, press the "Print Screen" key on your keyboard.  Then from the START button, bring up PROGRAMS, then ACCESSORIES, and there should be a PAINT program. Run this program (or any other imaging editor). When the program displays the PAINT screen, press the Cntl-V (paste) keys. The screen image will be displayed on the paint program. Then the image may be printed, or cropped and pasted into other applications such as MS WORD.

The Excel option will print the file being accessed providing the report calling it is based on a single – level database.  The database is printed without modification, and that means that the internal fields like “uniq_key” will also be included in the excel file.  When there are multiple databases included in the report, and there are filters and queries involved, the excel button will actually print to a text file that looks like the report.  The user can then convert to an excel file if they wish.

Will there be a capability to print text and graphics?

For Ver 3.5 and higher, the user is able to print out text and graphics using Acrobat in Inventory Control, Materials Requirements Planning, Routing, Project Data Management and Standard Process Specifications.  Please refer to the following procedure manuals:  Inventory Control Management, Materials Requirements Planning Management, Shop Floor Tracking Management and Production Planning Management.