Fm3 unable to open upg file

If you cannot open the FM3 file on your computer - there may be several reasons. The first and most important reason the most common is the lack of a suitable software that supports FM3 among those that are installed on your device. A very simple way to solve this problem is to find and download the appropriate application. The first part of the task has already been done — the software supporting the FM3 file can be found in the table. Now just download and install the appropriate application.

The inability to open and operate the FM3 file does not necessarily mean that you do not have an appropriate software installed on your computer. There may be other problems that also block our ability to operate the Lotus Release 3.

Below is a list of possible problems. It can be very frustrating. Yet such problems, not only with UPG files, can be addressed in a standard way. Follow the steps below and we can guarantee that your problem with opening UPG will be resolved! The file with extension. UPG is used by devices and programs to introduce updates.

Please note that this extension is used by various applications and equipment, so you should know which file is intended for which recipient. Below is a list of actions user should pursue in order to resolve most common problems. After the application has been installed, the system should automatically open UPG files with given application. How to open a UPG file? Update Unable to open UPG files with the associated software program or see an error than try updating the associated software Do not If none of the applications in your Windows were able to open UPG file do not change file extension because by changing file extension you are corrupting the file.

In case you already changed the extension you can revert it back to UPG by renaming the file. Incorrect associations are the cause of many UPG file errors. Obviously you'll need to create a new name for your BLOB file as well. Copy the table structure in the dct, and delete the BLOB in the original table structure and increment the version number.

Create the relationship between the two tables. Note: You'll have all the original fields in this table - but you can ignore these. In your program: Before FM3 kicks in i. Use Multi-Proj's Driver Substitution features to build multi-driver support into your app. Tip: Multi-Proj comes with a Driver Substitution feature. This means you can generate multiple exe's from 1 app or multi-dll apps , and 1 dct.

For more information, see the Multi-Proj docs. CScan Description CScan is a program for scanning and editing data files. Screenshot: Note: If you're getting an Error 47 or D when attempting to browse a file, then it probably means that your file declaration does not match that of the UPG. This is normally due to either a restored backup without the UPG.

Formatting To change the formatting of a column, after opening a file, point to that column and press Ctrl-F, or Ctrl-P. You can enter any standard Clarion picture. To change the contents of a field simply type the new contents over the existing contents. Note: Because CScan saves the format of your layout as you set it up, this can cause problems in the future - particularly if you hide columns or alter column orders.

If the file browse gets completely out of hand, you can modify the c-scan. Security To prevent unwanted scanning by your end user, C-Scan is protected using a simple password. The password is "SCAN". This is not meant as a security device, but to stop users accidentally scanning, and possibly editing files. To turn off this feature go to Preferences in the Help menu. If you want to give your users access to C-Scan, but you don't want to give them the SCAN password, then there is a dynamic alternative.

C-Scan has a "password of the day" feature. This password is calculated as follows; Take Today's date, and write it in D11 format i. If you want to protect your files from scanning by a sophisticated user, or another Clarion user, then use the Owner feature to encrypt your data files. Searching and Replacing C-Scan includes the ability to search a column for a matching entry.

In addition to this you can also do Partial and Anywhere searches. A Partial search will find a match, even if the search string is only part of an actual field. In other words a partial search of the word Cape will return a match in the string CapeSoft. An Anywhere search allows you to search all the fields for the required value. If this is switched off then only the highlighted column will be searched.

Choose the Search menu option after opening a file to search the file. Search and Replace is also supported. Distribution You are free to install CS. Exe on any computer, provided that an FM3 enabled application is running on that computer. This means that you can install C-Scan on your clients computer which can assist you with debugging, and supporting your program. C-Scan is compiled in local mode, and doesn't require any DLL's.

Btrieve The current release of C-Scan does not support Btrieve. These DLL's are included in the cs. Tps file. This is a useful debugging tool to see why a particular file won't upgrade. It is not intended as an End-User tool, but rather as a tool to assist developers. This is typically useful where some versions of tables exist in a UPG.

Print File Layout To print a copy of the file layout, for any particular version of the file, simply highlight the file and choose "File Layout" from the Reports menu.

Analyse File Changes To view an analysis of the changes to a file structure, highlight the file label and choose "Analyse File Changes" from the Reports menu.

This lists all the versions of the file, and the differences between the versions. This means that you can install UpgView on your clients computer which can assist you with debugging, and supporting your program. All FM3 errors are now prepended with the "FM3" identifier in some way, i.

If you are getting errors without a reference to FM3 in them, then they are not FM3 errors. If you are not convinced of this, use the FM3 Debugging functionality to see if the error appears there. If it does, send the Debuglog, together with the error screenshot, and detailed description of how to repeat the error to Support.

Compiler Errors C7 specific compile errors Assertion failed on line: in file abfile. Shall I GPF? M Unable to open file. Errorcode 90 received. Are you sure your Connection details are correct? Restart program to invoke AutoFIX. M Could not create Oracle TableSpace!

M FM3 encountered errors during file structure upgrade. Please review the "Debugging" and "Support" sections in the FM3 Documentation, or contact your application vendor for technical support! FM3 cannot manage this file! Contact your applciation supplier for details. Please upgrade your Program. Ending Program! Oracle does NOT support this datatype. Please update your dictionary definition to datatype REAL.

Error: Invalid Filename Press OK to end this application. Solution: You can safely click on No, then there are 2 ways to eliminate these errors: Go to your Project Properties and turn off debugging by "Building Release System", or setting Debug mode to "Off".

Comment out the assert on that particular line in the abfile. Cause: The main program module is too big for the compiler. Reason: You're possibly using FM3 on a very large dictionary with lots of aliases and FM3 user options.

This causes FM3 to generate a lot of initialization code. See the VLDS section of the docs for details on how to do this. Reason: There is no project define including the file driver into your application. Cause: You have more than 1 field in a file with the same External Name. Reason: SQL requires a unique field name for each field in a table.

If you have not uniquely assigned an external label for each field, this will cause a GPF in the conversion of the table. Solution: Go to the dictionary, and ensure all fields have unique External Names across the file. Cause: You file declaration is using a datatype that is not allowed with the specified driver.

Solution: If you are manually editing your dictionary then you should never see this message, however if you have used a 3rdparty tool to convert your dictionary to a different driver, then you may have some field types that are invalid for the new file driver.

The compiler simply warns you of an invalid data type for the new file driver. If you continue compiling you will probably get an Error 47 or D when FM3 tries to convert the file.

Invalid in 'MyFile' of driver: MyFileDriver External group names were always overlooked by the compiler until recently. If you have a really good reason for an external group name, then ignore this assert - however you will probably experience a GPF in the file-conversion process. OBJ Repeated for a number of functions Cause: The FM3 lib is not being linked into the project Reason: You're probably compiling in 16 bit mode - or else you have removed the FM3 template from the application.

Solution: Change your project to 32 bit mode. FM3 only supports 32 bit applications. This filename is set for each table when you upgrade your dictionary using BDE.

Either you have not used BDE to do the conversion to SQL in which case the filename is not set to use the variable - or else you have the 'Generate File Declarations in Modules' checkbox in the Global Properties - file tab checked Solution: Make sure that the 'Generate File Declarations in Modules' checkbox in the Global Properties - file tab is unchecked.

You need to check the 'Generate all file declarations' checkbox on the FileControl tab of your application's Global Properties. If you're using Multi-Proj's Driver Substitution feature?

Solution: Check the project to see which FM3 lib is being linked into your program, and then search your drive for that lib. You've handcoded code using these two variables which changed in 3. FM3 will be therefore unable to add non-unique constraints to the SQL backend if there are duplicates in the dictionary, thus FM3 checks the dictionary for you to find non-unique external names. You have at least one other template that is trying to include the ODBC function library into your application.

LIB' checkbox. This will only apply to local mode applications. If you have 2 files in your dct with the same first 8 letters - you'll get both tables using the same file. The second table to open the file will get an error 47 or D - because the structure is different.

FM3 is warning you about this so you don't get to this place - and wonder why you're getting error 47 or D Solution: Either specify a filename in the dct or you can add the NoAutoNameCheck file user option to one or both of the tables. C7 specific compile errors Clarion 7 has converted your c6 application erroneously. This is normally fairly easy to solve. Close your application and the C7 IDE. Open the folder wherein your application resides using Windows Explorer.

Make a backup of the files in the folder. Re-run the conversion. FM3 connects to the SQL backend, but when it tries to upgrade datatables, it hangs - or it hangs while trying to connect to the backend My program hangs as it upgrades a table.

My program hangs at the Connect window after I click the connect button. I am installing my FM3 enabled app on a Tablet , and my app is hanging, or getting an error: unable to open upg. This is causes a problem with the Clarion Threading issues.

Ensure you are only opening FM3 managed files on new threads. Change these to Strings. FM3 connects to the SQL backend, but when it tries to upgrade datatables, it hangs - or it hangs while trying to connect to the backend Check that you have correctly named your server that FM3 is connecting to the correct server.

Make sure you've put a! A logon window will also be displayed. If you do do this, then you need to re-import the Connect window into your application, and set the Server Name in the connect window options at runtime to the named instance of the server.

It is important that when using the IPAddress in the Server, that the Server is entered correctly with the named instance. If you are connecting from a remote machine, you may need to enable the Guest account. If you are using the default port, then make sure the port is set to 0 on the connect window settings.

If you have just upgraded to Clarion 11 or later, then the loading of 3rdparty DLLs has moved, and so we've had to change when the Connect window is called. There's a couple of reasons that this could be occurring: You are using Superfiles, and you are attempting a table upgrade that's in the superfile while another table in the same superfile is already open. The most simple work around is to convert all the tables on application startup - otherwise, you need to open and close each file in case of upgrade - before starting your procedures.

To workaround this, you can switch off this template on the local procedure you're using to upgrade the file. There's a couple of reasons that this could be occurring: You could have omitted to ensure that the Project Define was set for the driver s that you've selected in the AutoUp tab. The workaround is to ship your development upg. Due to a possible bug in Clarion 6, you need to add the FM3 Global Extension to your exe app as well as your data dll app.

Make you sure you check on all the necessary driver support, but leave the Connect Procedure blank in the exe extension. If I rename the exe, it works for sometime but then starts GPFing like the first one. You are probably using TPS files - and one of the files has reached the 2Gigabyte limit.

AutoFix is registering it as a corrupt file - and when the application runs, it goes to the RuntimeFileManager for you to "fix" the file, and GPFs on file open. Index out of range If you're using SQL files, one of your files' version number, may have gone backwards. Cause: FM3 cannot identify the driver specified for the file it's attempting to manage. Solution: 2 options: Go the Global Extension and ensure that all file drivers in your dictionary past and present are checked on.

See the Technical Reference for details. Solution: Check the implementation for your setup in the AutoUP section. Error: Possible file change without changing File Version number. Reason: You've made changes in the dictionary, and forgotten to increment the version number for the file, or the default clw of the data dll or exe for single exe applications was not re-generated.

Solution: FM3 can upgrade the file if necessary, but you will not be able to upgrade again unless you fix the error by performing the following step without changing the structure. Go the dictionary, and increment the version number for this file. Then recompile. If you still get this error, then delete the default clw module of you data dll or exe for single exe applications. Sometimes clarion does not regenerate the clw if you just changed the version number.

If you still get this error, then probably the best thing is to use UPGViewer to check the version numbers for that table inside the UPG. That will show you what the last version number for that those files is inside the UPG. For more info, see How to make basic file structure changes. If the errorcode is 3 , then the most likely reason is that the path specified for the upg. If you specified the upg. I know, I know. I've lost count of the folks who've assured me the folder is there, but the above test fails.

This is the second most common reason for access denied. If the errorcode is 90, then it probably means that the file is corrupt. Your options are in recommended order a restore a file from backup b copy a upg. If one TPS file is corrupt then chances are other may be too, so inspect your data carefully after the program starts running.

Reason: You have not specified a file prefix for this file in the dictionary. FM3 needs a file prefix for each file. Alternatively you may have handcoded a file into your application. FM3 replaces the Clarion open function with the FM3 - so all file opens proceed through it. If you have a table without a prefix, then FM3 is unable to determine whether the file is in the "Used File" list or not.

Error: Unable to upgrade file - no file name available Cause: FM3 cannot copy your data to a temporary file. Reason1: FM3 renames your data file to another name before upgrading.

If none of these filenames are available i. Solution1: You probably have the "Don't remove old versions" check box checked on in the Global Extension. Solution2: Check the permissions settings on the machine that houses the data for the user that accesses the data. Make sure that that user has file create, remove, read and write access all allowed. Reason: FM3 could not create and open the destination data file. Reason: FM3 could not open the destination data file.

Reason: FM3 could not read the source data file. Reason: FM3 experienced an error while writing the data out to the destination file. Reason: A structure exists in the upg. Check on all drivers used in the app, both in the past and present. Cause: FM3 has detected a possible Downgrade about to take place.

See Downgrading Files for info. Solution: Click Ignore to continue with downgrade. Click Abort to abort the program immediately without downgrading. Error: "File has no Prefix" Are you using encryption for these files? If so read up on using AutoUp with encrypted files here, as you probably aren't setting the variable passwords soon enough. These variables must be primed before the file is opened.

Error: "The data file is Invalid" Are you using encryption for these files? Error: File Corrupt. Solution: Restart the program. Solution: You are highly unlikely to receive this error, as FM3 automatically handles most of the common File Open errorcodes.

Cause: The program is trying to open an MDI window before the frame exists, or when no frame exists. Reason: FM3 initialises the RuntimeFileManager window before the frame opens when it has detected a possible file corruption.

Error: M Memo file missing Reason: Some flatfile systems have a separate physical file for the memo contents. If this memofile is missing, then you will get this message. The memory required is larger than the maximum specification - this normally means that the file is corrupt.

Solution: Restore the file from backup. Error: FM3: Unable to upgrade. Access to the existing file has been denied Cause: FM3 requires exclusive access to data files in order to upgrade them. Reason: Another program has access to the data files either another instance of your application Solution: Ensure that all users have quit the program before upgrading. Error: This record was changed by another station. Those changes will now be displayed.

Can't fix Encrypted files Fixing encrypted files means that your encryption code is passed to TPSFix via a command line parameter. This means that your encryption code can be detected and is therefore not secure.

You can allow fixing of encrypted files check the "Allow fixing of encrypted files" checkbox in the RunTimeFileManager control template - but be aware that this will be exposing your encryption code. If you get Errorcode 90 on a TPS file, then it means that either the file is encrypted and the encryption code has changed - so FM3 can't read the file - or the file is corrupted.

If it is already registered refresh the registration. For farther details see the documentation for the IP driver. M Error: File not in Manageable Zone! FM3 can only manage one database at a time. If the database name for a specific file does not match the current database, then FM3 will not be able to convert that database. You need to either: Move the offending table to the database that will be managed. This error will occur if FM3 attempts to insert or modify a record into the table.

Depending on what the file error is, will depend on why the insert failed. This syntax is compiled at runtime in order to re-structure the backend.

We have endeavored to cater for as many exceptions as possible, but all the supported backends have different limitations and unique quirks. Occasionally, FM3 will therefore compile a statement based on changes to the dictionary, which cannot be performed on the backend and which it does not detect as illegal. Let us know about these exceptions and we will build in a check for that specific condition before the SQL statement is compiled.

Please inform: support at capesoft dot com , and we will endeavor to support that field type so long as it can be matched to a Clarion datatype. A non-fatal error occurred when FM3 performed some file structure changes on the backend. This will be displayed in the logfile. The database is corrupt and needs to be repaired. Sometimes this connection cannot be re-established again. You need to either: Force the datatype to a datatype that the backend will support as a component of keys use ForceSQLDataType for this.

Remove that particular field from the key's components. If you get this message, then you need to either: remove the key from the dictionary, remove certain fields from the key's components, remove the attribute that is forcing the key to be populated on the backend either the DCTMasterOfKeys or Unique key. The best is to change the External name of the key in the dictionary.

Generally a good idea is to use: file-prefix underscore and keyname in the external key name. M Attempting an illegal field type conversion. This normally occurs when there is a pre-existing database - and now you've added FM3 to your application to manage the database.

If the field is correctly typed in the database, then you need to use the ForceSQLDataType feature to force the field to the unconventional datatype. Otherwise, you need to delete the field from the database. You have a variable type of text in the SQL Server.

After importing, the variable type used is a BLOB. FM3 suggests implementing SafeUpdate for automatic program file upgrades across networks!

Cause: The application's file definitions are out of date or old, you've imported the structures from your db to your dct, you've restored a copy of your dct with an old version , or you've decremented the Version number of a particular file never, ever do this.

Reason: Possibly another site has a newer version of the exe which has already updated the SQL Backend, but this exe has older file definition versions. Solution: Use SafeUpdate to implement automatic program file updates across networks. Alternatively, manually ensure your exe is up to date. This will be re-created by FM3 again. Alternatively, if this database is indeed not supported, disable FM3. See the Debugging section. Solution: Check User Access Rights. Check that the SQL Server is online.

If you are unable to determine the problem, send a Debuglog to CapeSoft Support. Error: Could not create Oracle TableSpace! Cause: An error occurred during creation of a the specified Oracle TableSpace. If you would like to fix the error, and not continue to create the table at this point: Click Abort.

Make the relevant changes to eliminate the error. Cause: FM3 cannot create the identity field. Solution: Go to the dictionary and ensure that you have only specified 1 field in the file as an Identity Column.

Cause: FM3 warns you of un-manageable datatype. Solution: Go to the dictionary and change it to a REAL, or some other supported datatype for this driver. FM3 supports what the driver can handle, and in some cases more! Error: FM3 encountered errors during file structure upgrade. Cause: 1 or more errors occurred during FM3's upgrade process. Reason: The reason would depend on the errors. Solution: Run a Debuglog of the behaviour.