Date   

Re: DXKeeper upgrade, from 15.9.9 to 16.1.5

Dave K2XR
 

Concur, same finding here.

On 6/19/2021 3:26:36 PM, Dave AA6YQ wrote:
Is it possible that compacting the file before the upgrade might help?

+ Experiments have not shown that compacting beforehand makes a difference.

73,
Dave, AA6YQ






Spotcollector not working

Marv Stasak
 

Spotcollector froze on me 2 days ago with no new spots coming in.  I made sure I was upgraded to the latest version, 8.8.8, and checked some back messages on this issue. It seemed the resolution was to remove spot.mdb from the spotcollector/database.  I did that but all I succeeded in doing was removing the spots already there; Spotcollector is still not populating. Suggestions?

73,
Marv, W5DT


Re: DXKeeper Window Missing - RESOLVED

Fred - NA2U
 

Thanks, Joe!

73 from the desert,

Fred/NA2U

---------- Original Message ----------
From: "Joe Subich, W4TV" <lists@subich.com>
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper Window Missing
Date: Sun, 20 Jun 2021 10:23:17 -0400


Close all DXLab Apps except Launcher and DXKeeper.
Open Launcher -> Config and click the "RESET" button in
the bottom row.

This will move DXKeeper and all its windows to the Primary
monitor.


73,

... Joe, W4TV


On 2021-06-20 10:09 AM, Fred - NA2U wrote:
I am using Windows 10 Pro with a 3-monitor configuration. Yesterday I removed one monitor, replaced it with a new one, and moved another monitor.

When I start DXKeeper its icon appears on the task bar but the window does not open on any monitor. I have tried the the various windows arrangement settings by right-clicking on the task bar without success. When I hover the mouse over the DXKeeper icon on the task bar it shows DXKeeper but the “preview” window is blank.

Any suggestions about how to recover? Thanks.

73 from the desert,

Fred/NA2U




____________________________________________________________
Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more

Truck Strikes People at Pride Parade, Killing 1
http://thirdpartyoffers.juno.com/TGL3141/60cf518ca9f80518c6ee7st03vuc1
Sunrise Hike Ends in Tragedy in Wyoming
http://thirdpartyoffers.juno.com/TGL3141/60cf518ccd5d4518c6ee7st03vuc2
Nationwide Events Mark Juneteenth
http://thirdpartyoffers.juno.com/TGL3141/60cf518cf0b82518c6ee7st03vuc3


Re: DXKeeper Window Missing

Joe Subich, W4TV
 

Close all DXLab Apps except Launcher and DXKeeper.
Open Launcher -> Config and click the "RESET" button in
the bottom row.

This will move DXKeeper and all its windows to the Primary
monitor.


73,

... Joe, W4TV

On 2021-06-20 10:09 AM, Fred - NA2U wrote:
I am using Windows 10 Pro with a 3-monitor configuration. Yesterday I removed one monitor, replaced it with a new one, and moved another monitor.
When I start DXKeeper its icon appears on the task bar but the window does not open on any monitor. I have tried the the various windows arrangement settings by right-clicking on the task bar without success. When I hover the mouse over the DXKeeper icon on the task bar it shows DXKeeper but the “preview” window is blank.
Any suggestions about how to recover? Thanks.
73 from the desert,
Fred/NA2U


DXKeeper Window Missing

Fred - NA2U
 

I am using Windows 10 Pro with a 3-monitor configuration. Yesterday I removed one monitor, replaced it with a new one, and moved another monitor.

When I start DXKeeper its icon appears on the task bar but the window does not open on any monitor. I have tried the the various windows arrangement settings by right-clicking on the task bar without success. When I hover the mouse over the DXKeeper icon on the task bar it shows DXKeeper but the “preview” window is blank.

Any suggestions about how to recover? Thanks.

73 from the desert,

Fred/NA2U
____________________________________________________________
Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more

Sunrise Hike Ends in Tragedy in Wyoming
http://thirdpartyoffers.juno.com/TGL3141/60cf4c25d78694c255979st04duc1
Nationwide Events Mark Juneteenth
http://thirdpartyoffers.juno.com/TGL3141/60cf4c266a114c255979st04duc2
Police Shoot Driver After Pickup Strikes Bicyclists
http://thirdpartyoffers.juno.com/TGL3141/60cf4c2629de34c255979st04duc3


Re: Adding the DXKeeper Comment Field to an Exported ADIF File

Dave AA6YQ
 

+ AA6YQ comments below

I'd like to include the logbook Comment field on the generated ADIF file with the number of characters (as shown below):

          <Comment:12>WV QSO PARTY

Searched through the documentation and I can't find anything on this.

 

+ See this entry:

https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#note

      73,

            Dave, AA6YQ


Adding the DXKeeper Comment Field to an Exported ADIF File

Steve / W1SMC <w1smc@...>
 

Searched through the documentation and I can't find anything on this.

I'd like to include the logbook Comment field on the generated ADIF file with the number of characters (as shown below):

          <Comment:12>WV QSO PARTY

Possible?  Or do I have to do this manually before I import my QSOs into my QRZ Logbook?

Thanks ..... Steve / W1SMC


Re: Print Other Station's Grid in QSL Notes - Multiple Grids

Alan N5NA
 

Thanks!


Re: Print Other Station's Grid in QSL Notes - Multiple Grids

Dave AA6YQ
 

+ AA6YQ comments below

I'm working on printing some QSLs for new 6m grids for stations not on LOTW. In the notes I'd like to print "TNX new grid DM81" or whatever. I have that figured out using QSL Message and the QSL Substitution Command <stationgrid>.

How can I include Grid2, Grid3, & Grid4 in the QSL message?

+ You must manually populate the "QSL Message" item for such QSOs.

73,

Dave, AA6YQ


Print Other Station's Grid in QSL Notes - Multiple Grids

Alan N5NA
 

I'm working on printing some QSLs for new 6m grids for stations not on LOTW.  In the notes I'd like to print "TNX new grid DM81" or whatever.  I have that figured out using QSL Message and the QSL Substitution Command <stationgrid>.

How can I include Grid2, Grid3, & Grid4 in the QSL message?  Some stations have been on a grid line or corner.

Thanks,

Alan N5NA


Re: DXKeeper Error

Russ Ravella
 

AAAAHHHHHaaaaaaaaa !! Oh my God that’s so good

On Jun 19, 2021, at 2:53 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

Worked like a champ. I don't understand how I wound up with such an old data file.

+ "When all other explanations fall short, blame Windows"

- Mark Twain

73,

Dave, AA6YQ






Re: DXKeeper Error

Dave AA6YQ
 

+ AA6YQ comments below

Worked like a champ. I don't understand how I wound up with such an old data file.

+ "When all other explanations fall short, blame Windows"

- Mark Twain

73,

Dave, AA6YQ


Re: DXKeeper Error

Pete W1RM
 

Worked like a champ. I don't understand how I wound up with such an old
data file.


Pete Chamalian, W1RM
W1rm@comcast.net

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, June 19, 2021 5:30 PM
To: DXLab@groups.io
Subject: QRE: [DXLab] DXKeeper Error

+ AA6YQ comments below

I have had to reinstall everything on my windows 10 machine thanks to a boot
error that just made a total mess.


Anyway, when DXKeeper starts, I'm getting a message VW-WAE award file
c:\DXLab\DXKeeper\Databases\CQWAE.txt contains an entry that does not
specify the region's continent.


The file shows this:

1,206,4U1V,ITU Vienna,CQ,WAE

2,248,IG9/IH9,African Italy,CQ,NoWAE

3,248,IT9,Sicily,CQ,WAE

4,259,JW/B, Bear Island,CQ,WAE

5,279,GM/S,Shetland Islands,CQ,WAE

6,390,TA1,European Turkey,CQ,WAE

7,296,YU8,Kosovo,CQ,WAE

What does this error tell me other than DKX can't figure out the continent
but I don't see that.


+ On 2019-02-14, I released DXKeeper 1485 with this enhancement:

"includes a by-continent analysis in the CQ DX Marathon progress report"

+ Implementing this functionality required appending an explicit
+ continent designator to each entry in the CQWAE.txt file residing
in DXKeeper's Databases folder:

1,206,4U1V,ITU Vienna,CQ,WAE,EU
2,248,IG9/IH9,African Italy,CQ,NoWAE,AF
3,248,IT9,Sicily,CQ,WAE,EU
4,259,JW/B, Bear Island,CQ,WAE,EU
5,279,GM/S,Shetland Islands,CQ,WAE,EU
6,390,TA1,European Turkey,CQ,WAE,EU
7,296,YU8,Kosovo,CQ,WAE,EU

+ Every DXKeeper update released since then has included the updated
+ version of this CQWAE.txt file. Why this file was not properly
installed along with everything else when you recovered from your recent
failure, I can't say.

+ You can obtain the current version of this file from

www.dxlabsuite.com/dxkeeper/CQWAE.txt

+ Terminate DXKeeper, delete the existing CQWAE.txt in DXKeeper's
+ Databases folder, download the above URL and save its contents to
a file named CQWAE.txt in DXKeeper's Databases folder, and then start
DXKeeper. Any joy?

73,

Dave, AA6YQ


QRE: [DXLab] DXKeeper Error

Dave AA6YQ
 

+ AA6YQ comments below

I have had to reinstall everything on my windows 10 machine thanks to a boot error that just made a total mess.


Anyway, when DXKeeper starts, I'm getting a message VW-WAE award file c:\DXLab\DXKeeper\Databases\CQWAE.txt contains an entry that
does not specify the region's continent.


The file shows this:

1,206,4U1V,ITU Vienna,CQ,WAE

2,248,IG9/IH9,African Italy,CQ,NoWAE

3,248,IT9,Sicily,CQ,WAE

4,259,JW/B, Bear Island,CQ,WAE

5,279,GM/S,Shetland Islands,CQ,WAE

6,390,TA1,European Turkey,CQ,WAE

7,296,YU8,Kosovo,CQ,WAE

What does this error tell me other than DKX can't figure out the continent but I don't see that.


+ On 2019-02-14, I released DXKeeper 1485 with this enhancement:

"includes a by-continent analysis in the CQ DX Marathon progress report"

+ Implementing this functionality required appending an explicit continent designator to each entry in the CQWAE.txt file residing
in DXKeeper's Databases folder:

1,206,4U1V,ITU Vienna,CQ,WAE,EU
2,248,IG9/IH9,African Italy,CQ,NoWAE,AF
3,248,IT9,Sicily,CQ,WAE,EU
4,259,JW/B, Bear Island,CQ,WAE,EU
5,279,GM/S,Shetland Islands,CQ,WAE,EU
6,390,TA1,European Turkey,CQ,WAE,EU
7,296,YU8,Kosovo,CQ,WAE,EU

+ Every DXKeeper update released since then has included the updated version of this CQWAE.txt file. Why this file was not properly
installed along with everything else when you recovered from your recent failure, I can't say.

+ You can obtain the current version of this file from

www.dxlabsuite.com/dxkeeper/CQWAE.txt

+ Terminate DXKeeper, delete the existing CQWAE.txt in DXKeeper's Databases folder, download the above URL and save its contents to
a file named CQWAE.txt in DXKeeper's Databases folder, and then start DXKeeper. Any joy?

73,

Dave, AA6YQ


Re: DXKeeper Error

w6de
 

None of your entries show the Continent.

On my system the file look like this:

 

1,206,4U1V,ITU Vienna,CQ,WAE,EU

2,248,IG9/IH9,African Italy,CQ,NoWAE,AF

3,248,IT9,Sicily,CQ,WAE,EU

4,259,JW/B, Bear Island,CQ,WAE,EU

5,279,GM/S,Shetland Islands,CQ,WAE,EU

6,390,TA1,European Turkey,CQ,WAE,EU

7,296,YU8,Kosovo,CQ,WAE,EU

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Pete W1RM via groups.io
Sent: Saturday, June 19, 2021 20:37
To: dxlab@groups.io
Subject: [DXLab] DXKeeper Error

 

I have had to reinstall everything on my windows 10 machine thanks to a boot error that just made a total mess.

 

Anyway, when DXKeeper starts, I’m getting a message VW-WAE award file c:\DXLab\DXKeeper\Databases\CQWAE.txt contains an entry that does not specify the region’s continent.

 

The file shows this:

 

1,206,4U1V,ITU Vienna,CQ,WAE

2,248,IG9/IH9,African Italy,CQ,NoWAE

3,248,IT9,Sicily,CQ,WAE

4,259,JW/B, Bear Island,CQ,WAE

5,279,GM/S,Shetland Islands,CQ,WAE

6,390,TA1,European Turkey,CQ,WAE

7,296,YU8,Kosovo,CQ,WAE

 

What does this error tell me other than DKX can’t figure out the continent but I don’t see that.


DXKeeper Error

Pete W1RM
 

I have had to reinstall everything on my windows 10 machine thanks to a boot error that just made a total mess.

 

Anyway, when DXKeeper starts, I’m getting a message VW-WAE award file c:\DXLab\DXKeeper\Databases\CQWAE.txt contains an entry that does not specify the region’s continent.

 

The file shows this:

 

1,206,4U1V,ITU Vienna,CQ,WAE

2,248,IG9/IH9,African Italy,CQ,NoWAE

3,248,IT9,Sicily,CQ,WAE

4,259,JW/B, Bear Island,CQ,WAE

5,279,GM/S,Shetland Islands,CQ,WAE

6,390,TA1,European Turkey,CQ,WAE

7,296,YU8,Kosovo,CQ,WAE

 

What does this error tell me other than DKX can’t figure out the continent but I don’t see that.


Re: DXKeeper upgrade, from 15.9.9 to 16.1.5

Dave AA6YQ
 

Is it possible that compacting the file before the upgrade might help?

+ Experiments have not shown that compacting beforehand makes a difference.

73,

Dave, AA6YQ


Re: DXKeeper upgrade, from 15.9.9 to 16.1.5

KA9JAC
 

Dave,

Is it possible that compacting the file before the upgrade might help?

73
Bob, KA9JAC

PS no issues here, Everything works as it should :-)

On 6/19/2021 1:42 PM, Dave AA6YQ wrote:
Old subject, new thread.

Might be able to shed some light on the issue. Here is my story.


When MODE was first extended from 8 to 12 chars, a few friends I 'support' had the failure during the expansion process.

In each case I received, I discovered (using Access 2007 ) that all processes were completed, but the temporaryfield4 was still in existence. So when DXkeeper started up, it complained of too many fields and exited gracefully. Deleting the field restored functionality and all was well under version 16.1.x

Until today...

Buddy sent his log, and I expected to find the same issue, but not so. Log contains approx 70k q's.

DXK error message upon conversion attempt is the same as reported in previous instances of this thread:

Examining the errorlog as suggested yielded this:

2021-06-19 12:33:46 > DXKeeper version 16.1.5
2021-06-19 12:33:46 > App.Path : C:\DXLab\DXKeeper
2021-06-19 12:33:46 > App.exe : DXKeeper
2021-06-19 12:33:46 > Module : C:\DXLab\DXKeeper\DXKeeper.exe
2021-06-19 12:33:46 > Operating System : Windows 10 Enterprise
(64-bit) build 19041
2021-06-19 12:33:46 > Locale ID : 1033 (0x409)
2021-06-19 12:33:46 > ANSI CodePage : 1252
2021-06-19 12:33:46 > OEM CodePage : 437
2021-06-19 12:33:46 > Country : United States
2021-06-19 12:33:46 > Language : English
2021-06-19 12:33:46 > DecimalSeparator : .
2021-06-19 12:33:46 > ThousandSeparator : ,
2021-06-19 12:33:46 > DXLab Apps :
2021-06-19 12:35:31 > Monitors : 3
2021-06-19 12:35:31 > Monitor 1
2021-06-19 12:35:31 > width : 1536
2021-06-19 12:35:31 > height : 864
2021-06-19 12:35:31 > dimensions : (0, 0)-(1536, 864)
2021-06-19 12:35:31 > Monitor 2
2021-06-19 12:35:31 > width : 1280
2021-06-19 12:35:31 > height : 720
2021-06-19 12:35:31 > dimensions : (1536, 5)-(2816, 725)
2021-06-19 12:35:31 > Monitor 3
2021-06-19 12:35:31 > width : 1280
2021-06-19 12:35:31 > height : 720
2021-06-19 12:35:31 > dimensions : (3072, 9)-(4352, 729)
2021-06-19 12:35:31.831 > program error 3035 in module DXLogModule.UpdateFields, theState = 105, UpdateFields = 4, SaveUpdateFields = : System resource exceeded.
2021-06-19 12:38:05.241 > Common.Terminate: DXKeeper shutdown


So I key in on the system resource exceeded clue.

Move to the machine with the most RAM in the house (16gb) and same error message is returned.

+ Microsoft uses a much broader definition of "System resource" than "available RAM".


Browsed the archives for the latest and read the thread generated by message # 201752 same subject as above.

Tell friend to send the log to you... but before he does, I decide to try another method...

Back to Access, open the log. Go to the QSO table,enter design mode, find the mode field ... change length from 8 to 12

Access wants me to save the changes and reopen the mdb. So I try...

Access throws an error similar to the errorlog report, but with a few suggestions as to why.

Either : You have changed the field to no duplicates, and there already were duplicates ( discarded since hey... it's mode ;) )

or : You have an insufficient number or locks available.... if you wish to try and fix this, look at this registry entry ( the access registry ) and change the value to a higher number ... with appropriate warnings on fooling with the registry.

So I look at the entry on my Access machine . The value name is maxlocksperfile and it was set to 9500 in the machine I was doing this on.


Not wishing to go any further, I zipped his log, sent it back to him, and told him to send it to you per suggestions seen fairly frequently.

He mailed it at the same time I posted this.

+ The only correlation I've been able to establish is that attempting to expand a log's Mode file from 8 to 12 characters is more likely to fail on a computer running Windows 10. DXKeeper running on Windows 7 has successfully upgraded every log sent to me, including one with more than 300K QSOs.

73,

Dave, AA6YQ




--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: DXKeeper upgrade, from 15.9.9 to 16.1.5

Dave AA6YQ
 

Old subject, new thread.

Might be able to shed some light on the issue. Here is my story.


When MODE was first extended from 8 to 12 chars, a few friends I 'support' had the failure during the expansion process.

In each case I received, I discovered (using Access 2007 ) that all processes were completed, but the temporaryfield4 was still in existence. So when DXkeeper started up, it complained of too many fields and exited gracefully. Deleting the field restored functionality and all was well under version 16.1.x

Until today...

Buddy sent his log, and I expected to find the same issue, but not so. Log contains approx 70k q's.

DXK error message upon conversion attempt is the same as reported in previous instances of this thread:

Examining the errorlog as suggested yielded this:

2021-06-19 12:33:46 > DXKeeper version 16.1.5
2021-06-19 12:33:46 > App.Path : C:\DXLab\DXKeeper
2021-06-19 12:33:46 > App.exe : DXKeeper
2021-06-19 12:33:46 > Module : C:\DXLab\DXKeeper\DXKeeper.exe
2021-06-19 12:33:46 > Operating System : Windows 10 Enterprise
(64-bit) build 19041
2021-06-19 12:33:46 > Locale ID : 1033 (0x409)
2021-06-19 12:33:46 > ANSI CodePage : 1252
2021-06-19 12:33:46 > OEM CodePage : 437
2021-06-19 12:33:46 > Country : United States
2021-06-19 12:33:46 > Language : English
2021-06-19 12:33:46 > DecimalSeparator : .
2021-06-19 12:33:46 > ThousandSeparator : ,
2021-06-19 12:33:46 > DXLab Apps :
2021-06-19 12:35:31 > Monitors : 3
2021-06-19 12:35:31 > Monitor 1
2021-06-19 12:35:31 > width : 1536
2021-06-19 12:35:31 > height : 864
2021-06-19 12:35:31 > dimensions : (0, 0)-(1536, 864)
2021-06-19 12:35:31 > Monitor 2
2021-06-19 12:35:31 > width : 1280
2021-06-19 12:35:31 > height : 720
2021-06-19 12:35:31 > dimensions : (1536, 5)-(2816, 725)
2021-06-19 12:35:31 > Monitor 3
2021-06-19 12:35:31 > width : 1280
2021-06-19 12:35:31 > height : 720
2021-06-19 12:35:31 > dimensions : (3072, 9)-(4352, 729)
2021-06-19 12:35:31.831 > program error 3035 in module DXLogModule.UpdateFields, theState = 105, UpdateFields = 4, SaveUpdateFields = : System resource exceeded.
2021-06-19 12:38:05.241 > Common.Terminate: DXKeeper shutdown


So I key in on the system resource exceeded clue.

Move to the machine with the most RAM in the house (16gb) and same error message is returned.

+ Microsoft uses a much broader definition of "System resource" than "available RAM".


Browsed the archives for the latest and read the thread generated by message # 201752 same subject as above.

Tell friend to send the log to you... but before he does, I decide to try another method...

Back to Access, open the log. Go to the QSO table,enter design mode, find the mode field ... change length from 8 to 12

Access wants me to save the changes and reopen the mdb. So I try...

Access throws an error similar to the errorlog report, but with a few suggestions as to why.

Either : You have changed the field to no duplicates, and there already were duplicates ( discarded since hey... it's mode ;) )

or : You have an insufficient number or locks available.... if you wish to try and fix this, look at this registry entry ( the access registry ) and change the value to a higher number ... with appropriate warnings on fooling with the registry.

So I look at the entry on my Access machine . The value name is maxlocksperfile and it was set to 9500 in the machine I was doing this on.


Not wishing to go any further, I zipped his log, sent it back to him, and told him to send it to you per suggestions seen fairly frequently.

He mailed it at the same time I posted this.

+ The only correlation I've been able to establish is that attempting to expand a log's Mode file from 8 to 12 characters is more likely to fail on a computer running Windows 10. DXKeeper running on Windows 7 has successfully upgraded every log sent to me, including one with more than 300K QSOs.

73,

Dave, AA6YQ


DXKeeper upgrade, from 15.9.9 to 16.1.5

Dave K2XR
 

Old subject, new thread.

Might be able to shed some light on the issue.   Here is my story.


When MODE was first extended from 8 to 12 chars, a few friends I
'support'  had the failure during the expansion process.

In each case I received, I discovered (using Access 2007 ) that all
processes were completed, but the temporaryfield4 was still in
existence. So when DXkeeper started up, it complained of too many fields
and exited gracefully.    Deleting the field restored functionality and
all was well under version 16.1.x

Until today...

Buddy sent his log, and I expected to find the same issue, but not so.  
Log contains approx 70k q's.

DXK error message upon conversion attempt is the same as reported in
previous instances of this thread:

Examining the errorlog as suggested  yielded this:

2021-06-19 12:33:46     > DXKeeper version 16.1.5
2021-06-19 12:33:46     > App.Path          : C:\DXLab\DXKeeper
2021-06-19 12:33:46     > App.exe           : DXKeeper
2021-06-19 12:33:46     > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
2021-06-19 12:33:46     > Operating System  : Windows 10 Enterprise
(64-bit) build 19041
2021-06-19 12:33:46     > Locale ID         : 1033 (0x409)
2021-06-19 12:33:46     > ANSI CodePage     : 1252
2021-06-19 12:33:46     > OEM CodePage      : 437
2021-06-19 12:33:46     > Country           : United States
2021-06-19 12:33:46     > Language          : English
2021-06-19 12:33:46     > DecimalSeparator  : .
2021-06-19 12:33:46     > ThousandSeparator : ,
2021-06-19 12:33:46     > DXLab Apps        :
2021-06-19 12:35:31     > Monitors          : 3
2021-06-19 12:35:31     > Monitor 1
2021-06-19 12:35:31     >    width          : 1536
2021-06-19 12:35:31     >    height         : 864
2021-06-19 12:35:31     >    dimensions     : (0, 0)-(1536, 864)
2021-06-19 12:35:31     > Monitor 2
2021-06-19 12:35:31     >    width          : 1280
2021-06-19 12:35:31     >    height         : 720
2021-06-19 12:35:31     >    dimensions     : (1536, 5)-(2816, 725)
2021-06-19 12:35:31     > Monitor 3
2021-06-19 12:35:31     >    width          : 1280
2021-06-19 12:35:31     >    height         : 720
2021-06-19 12:35:31     >    dimensions     : (3072, 9)-(4352, 729)
2021-06-19 12:35:31.831 > program error 3035 in module
DXLogModule.UpdateFields, theState = 105, UpdateFields = 4,
SaveUpdateFields = : System resource exceeded.
2021-06-19 12:38:05.241 > Common.Terminate: DXKeeper shutdown


So I key in on the system resource exceeded clue.

Move to the machine with the most RAM in the house  (16gb)  and same
error message is returned.

Browsed the archives for the latest  and read the thread generated by
message #  201752  same subject as above.

Tell friend to send the log to you...      but before he does, I decide
to  try another method...

Back to Access, open the log. Go to the QSO table,enter design mode,
find the mode field ...  change length from 8 to 12

Access wants me to save the changes and reopen the mdb.   So I try...

Access throws an error similar to the errorlog report, but with a few
suggestions as to why.

Either :   You have changed the field to no duplicates, and there
already were duplicates  ( discarded   since hey... it's mode ;) )

or :  You have an insufficient number or locks available....  if you
wish to try and fix this, look at this registry entry  ( the access
registry )  and change the value to a higher number ... with appropriate
warnings on fooling with the registry.

So I look at the entry on my Access machine .  The value name is
maxlocksperfile   and it was set to 9500 in the machine I was doing this on.


Not wishing to go any further, I zipped his log, sent it back to him,
and told him to send it to you per suggestions seen fairly frequently.

He mailed it at the same time I posted this.

   XR Dave

1841 - 1860 of 203861