Access LCTA Known Bugs

[ Back to the Access LCTA main page ]

[Submit a Bug Report]

Date format may cause problems when uploading handheld data.

If the Windows short date format is set to something other than month, day, year the date read from the handheld data file may be entered into the database incorrectly. In some cases data may not load. For example, if the date inside the handheld data file is set to 6/1/2004 (June 1, 2004) and the Windows short date format is set to d/M/yyyy then the date loaded in the database will be January 1, 2004.

Resolution

Change the Windows short date format to M/d/yyyy. This is set under the Regional Options section of the Control Panel in Windows.

"You don't have the necessary permissions to use the  tmp_Analysis_Disturbance object".

This error was shown when running the Ground Disturbance Analysis by year. The error was related to the ownership of the object as has been corrected in Version 1.0 Beta 3 B (second release).

Error in the code for calculating the K factor

This occurs when only one plot exists for a soil series and there is no standard deviation. 

Resolution

Access LCTA Version 1 Beta 3 B now checks for null values, reports an error, and inserts -1 into the SoilMast table.

"Invalid procedure call..." in USLE analysis

This error is caused by negative values of slope and/or slope length in the SoilLS table.

Resolution

The equation for calculating the LS value will not handle negative numbers.
Access LCTA Version 1 Beta 3 B now checks for negative values, reports an error, and inserts -1 into the tmp_erosion table for LS.

"Don't have necessary permissions to use the 'Crosstab_USLE' object........." in the USLE analysis

This error is related to the owner of the query.

Resolution

In Access LCTA Version 1 Beta 3 B ownership was corrected.

"Run-time error 453. Can't find DLL entry point adh_apigetDesktopWindow in user 32"

This error was shown when trying to produce graphs from an analysis data view form. 

Resolution

The code that is used to center forms will not work on forms designated as popup forms. In Access LCTA Version 1 Beta 3 B the graph template was changed to a non-popup form to support centering.

invalid page fault in module VBA332.DLL

You may get the following message in various parts of the program. This is a common problem with many users of Access 97 and the problem is under investigation.

Details: MSACCESS caused an invalid page fault in
module VBA332.DLL at 0137:65182a15.
Registers:
EAX=00000035 CS=0137 EIP=65182a15 EFLGS=00010286
EBX=03344968 SS=013f ESP=0062e1c4 EBP=80000068
ECX=7fffffff DS=013f ESI=0334536c FS=3427
EDX=00000068 ES=013f EDI=03345368 GS=0000
Bytes at CS:EIP:
8b 58 1c 81 e5 fc ff ff 7f c1 ed 02 85 db 0f 84
Stack dump:
0062e1f8 7fffffff 0334536c 03344968 651a8dc3 03345368 00000000
0000006e 03344968 00000098 00451a14 00409ec4 0040afa4 0062e25c
651a8d39 03344968

Resolution

If you are using a Beta version of Access LCTA try installing a newer version (download page).  There is also an undocumented feature of Access that can be used to correct this error, which is discussed below. 

If your Access LCTA program is crashing for no apparent reason here is
something to try. This process will recompile the code to better match
your system.

It seems that when the program crashes the first time the program
becomes more prone to crashes. I expect that some part of the program
is becoming corrupt and has something to do with some of the system
files Access uses.

First, you need to replace the current copy of the Access LCTA program
(lcta.mdb) with a fresh copy. You can do this by re-installing the
program.

Select the Win95, or NT 4.0, Start button then Run. When the Run dialog
box opens enter the following in the text field (including the quotes):

"D:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /wrkgrp
c:\itam\accesslcta\lctasys.mdw /decompile c:\itam\accesslcta\lcta.mdb

Change the paths to reflect those on your computer. Then select the OK
button. Sign on as usual. You will see the word "Saving", and the
progress bar, in the lower left hand corner. Then finally a message
will appear telling you that the code has been converted to your version
of visual basic, select OK. The application will then open as normal.
If you are asked if you want to attach tables select no. At the splash
screen select the right arrow to get to the main form. Then select the
close button to close the main form, the button that looks like a door.
Press the F11 key, this will open the database window. Select the Forms
tab and find the form named Admin_Compile. Select it and the Open
button. Now select the Compile button and then Yes to compile. When
the code has been compiled a message will let you know. Now close down
Access and start the program from the icon as you normally do.

Starting with Version 1.0.0 (final) the Access LCTA installation program will create an icon in the Access LCTA folder for running the decompile process listed above.  Refer to the readme.txt file after installing Access LCTA.

Button text is not completely visible on some buttons

On some forms the text that appears on buttons is cut off (i.e. too large to appear completely on the face of the button).

Resolution

Access LCTA Version 1.0 Beta 2 has been changed to adjust the size of forms and controls to match the user's screen resolution.

Selecting the Utilities bottom on the main form causes the program to crash

Some people have reported that entering the Utilities form causes the program to crash or hang.

Resolution

Access LCTA Version 1.0 Beta 3 has been changed to fix this error. The MS Common Dialog Control was removed from the form. This will hopefully fix the problem.

Forms open in the right portion of the screen. They are not centered.

Access LCTA Version 1.0 Beta 2 included code to adjust the size of forms and controls to match the user's screen resolution. On some systems this caused the form to open not in the center of the screen, but to the right. In some cases part of the form was located off the screen.

Resolution

Code has been added to Access LCTA Version 1.0 Beta 3 to center for the forms.

In the Plot Information module the opion All Years for Selected Plot does not perform correctly.

The Plot Information module contained an error. Plot Information is found under the Information tab of the Analyses dialog. The option All Years for Selected Plot      did not perform correctly.

Resolution

Access LCTA versions 1.5 (Access 97) and 2.1 (Access 2000/XP) contain the bug fix.

No Maintenance Activity not imported from handheld data file in short-term monitoring.

The Load Handheld Data procedure did not bring in No Maintenace Activity, when selected in the data logger program, for short-term monitoring.

Resolution

Access LCTA versions 1.5 (Access 97) and 2.1 (Access 2000/XP) contain the bug fix.

Check for Missing Plots procedure incorrectly reported missing ErosEvid plots.

The Check for Missing Plots procedure incorrectly report missing erosion evidence (ErosEvid) when maintenace activity (MaintAct) was missing.

Resolution

Access LCTA versions 1.5 (Access 97) and 2.1 (Access 2000/XP) contain the bug fix.

[Top]