sluggish responsiveness of vb app using office automation

  • Thread starter francois keyeux
  • Start date
F

francois keyeux

Hi,

i have a small application created using VB which uses Access97 via DAO and
MSJet (it executes queries and print reports, and has one data entry screen
accessing a table via msjet i believe)

all was fine when i created this long time ago using VB5 and i believe
versions 25x of the data access stuff
needing to work on this using VB6 and more recent versions of the data
access stuff, namely versions 35x as you can see in list below, the app
works fine on my development machine, but is now very sluggish and slow on
the user machine (which is using Win98-2ndEd)

i was hoping anyone might have experienced this and/or a clue as the cause
of this

my guess would be a compatibility issues between the versions; upgrading to
recent version of office is last resort option as i can not justify the
expense to the customer just to be able to run this small custom app

thank you much
francois



Please find below the content of the setup list, listing the various dlls
used:
(i have also attached this small txt file to the msg)

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=KeyBS.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,7/15/00 12:00:00
AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00
AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),,,6/1/99 12:00:00
AM,326656,4.22.0.0
[email protected],$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00
AM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 12:00:00
AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00
AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00
12:00:00 AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,2/23/04
12:00:00 AM,1386496,6.0.97.82

[IconGroups]
Group0=KeyBS
PrivateGroup0=-1
Parent0=$(Programs)

[KeyBS]
Icon1="KeyBS.exe"
Title1=KeyBS
StartIn1=$(AppPath)

[Setup]
Title=KeyBS
DefaultDir=$(ProgramFiles)\KeyBS
AppExe=KeyBS.exe
AppToUninstall=KeyBS.exe

[Setup1 Files]
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04
12:00:00 AM,152848,6.1.97.82
[email protected],$(WinSysPath),,$(Shared),6/18/98 12:00:00
AM,89360,6.0.81.69
[email protected],$(WinSysPathSysFile),,,6/13/00 12:00:00
AM,415504,3.51.2404.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/27/04 5:08:01
PM,262144,3.51.623.0
[email protected],$(WinSysPathSysFile),,,1/10/04 7:37:02
AM,380957,6.0.72.9589
[email protected],$(WinSysPathSysFile),,,3/16/04 2:44:16
PM,30749,6.0.1.9431
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,139264,3.51.623.0
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,36864,3.51.623.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,6/13/00 12:00:00
AM,1046288,3.51.2723.0
[email protected],$(MSDAOPath),$(DLLSelfRegister),$(Shared),4/27/98
12:00:00 AM,570128,3.51.1608.0
[email protected],$(MSDAOPath),$(TLBRegister),$(Shared),5/15/98 12:00:00
AM,73184,0.0.0.0
[email protected],$(WinSysPath),,$(Shared),7/11/97 12:00:00
AM,311296,8.0.0.3512
[email protected],$(AppPath),,,10/1/04 5:04:19 PM,188416,2.0.0.0

; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
 
V

Val Mazur

Hi,

If nothing was changed in a code and it is fast on your PC, then I would
suspect that database in production does not have all the required indexes
for the tables, which your database has.

--
Val Mazur
Microsoft MVP


francois keyeux said:
Hi,

i have a small application created using VB which uses Access97 via DAO
and
MSJet (it executes queries and print reports, and has one data entry
screen
accessing a table via msjet i believe)

all was fine when i created this long time ago using VB5 and i believe
versions 25x of the data access stuff
needing to work on this using VB6 and more recent versions of the data
access stuff, namely versions 35x as you can see in list below, the app
works fine on my development machine, but is now very sluggish and slow on
the user machine (which is using Win98-2ndEd)

i was hoping anyone might have experienced this and/or a clue as the cause
of this

my guess would be a compatibility issues between the versions; upgrading
to
recent version of office is last resort option as i can not justify the
expense to the customer just to be able to run this small custom app

thank you much
francois



Please find below the content of the setup list, listing the various dlls
used:
(i have also attached this small txt file to the msg)

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=KeyBS.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,7/15/00 12:00:00
AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98
12:00:00
AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),,,6/1/99 12:00:00
AM,326656,4.22.0.0
[email protected],$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00
AM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 12:00:00
AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99
12:00:00
AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00
12:00:00 AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,2/23/04
12:00:00 AM,1386496,6.0.97.82

[IconGroups]
Group0=KeyBS
PrivateGroup0=-1
Parent0=$(Programs)

[KeyBS]
Icon1="KeyBS.exe"
Title1=KeyBS
StartIn1=$(AppPath)

[Setup]
Title=KeyBS
DefaultDir=$(ProgramFiles)\KeyBS
AppExe=KeyBS.exe
AppToUninstall=KeyBS.exe

[Setup1 Files]
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04
12:00:00 AM,152848,6.1.97.82
[email protected],$(WinSysPath),,$(Shared),6/18/98 12:00:00
AM,89360,6.0.81.69
[email protected],$(WinSysPathSysFile),,,6/13/00 12:00:00
AM,415504,3.51.2404.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/27/04
5:08:01
PM,262144,3.51.623.0
[email protected],$(WinSysPathSysFile),,,1/10/04 7:37:02
AM,380957,6.0.72.9589
[email protected],$(WinSysPathSysFile),,,3/16/04 2:44:16
PM,30749,6.0.1.9431
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,139264,3.51.623.0
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,36864,3.51.623.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,6/13/00
12:00:00
AM,1046288,3.51.2723.0
[email protected],$(MSDAOPath),$(DLLSelfRegister),$(Shared),4/27/98
12:00:00 AM,570128,3.51.1608.0
[email protected],$(MSDAOPath),$(TLBRegister),$(Shared),5/15/98 12:00:00
AM,73184,0.0.0.0
[email protected],$(WinSysPath),,$(Shared),7/11/97 12:00:00
AM,311296,8.0.0.3512
[email protected],$(AppPath),,,10/1/04 5:04:19 PM,188416,2.0.0.0

; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
 
F

francois keyeux

good morning, here is my feedback:

i'm sorry but i don't quite understand how this can apply to my situation:
the database file is a standalone access97.mdb file which contains the
tables, one report layout and a collection of queries; the executable is one
standalone exe compiled with VB60
* how could it be missing indexes, i made no changes to neither database
layout/settings nor table designs
* all the tables except 1 data table are used to process report data; there
is only one table accumulating data records
* also, the main data table contains only one thousand records or so, so it
is not a huge database by far

on the other hand, and now that i think of it, yes the table has two indexes
and one is a primary key; in addition both indexes are set to refuse
duplicate key values - so yes i guess i see your point and i could try to
remove the primary key and/or removing the dup key check
-> i gotta physically go to the customer site to test your suggestion; will
do and let u know, but donno exactly when that will happen
-> and i gotta think about this because i need another way to enforce unique
records, and using this access feature was an immediate way to do this; even
if that the problem, still does not answer why okaye on my machine and not
on customer machine

~f~



Hi,

If nothing was changed in a code and it is fast on your PC, then I would
suspect that database in production does not have all the required indexes
for the tables, which your database has.

--
Val Mazur
Microsoft MVP


francois keyeux said:
Hi,

i have a small application created using VB which uses Access97 via DAO
and
MSJet (it executes queries and print reports, and has one data entry
screen
accessing a table via msjet i believe)

all was fine when i created this long time ago using VB5 and i believe
versions 25x of the data access stuff
needing to work on this using VB6 and more recent versions of the data
access stuff, namely versions 35x as you can see in list below, the app
works fine on my development machine, but is now very sluggish and slow on
the user machine (which is using Win98-2ndEd)

i was hoping anyone might have experienced this and/or a clue as the cause
of this

my guess would be a compatibility issues between the versions; upgrading
to
recent version of office is last resort option as i can not justify the
expense to the customer just to be able to run this small custom app

thank you much
francois



Please find below the content of the setup list, listing the various dlls
used:
(i have also attached this small txt file to the msg)

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=KeyBS.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,7/15/00 12:00:00
AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98
12:00:00
AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),,,6/1/99 12:00:00
AM,326656,4.22.0.0
[email protected],$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00
AM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 12:00:00
AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99
12:00:00
AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00
12:00:00 AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,2/23/04
12:00:00 AM,1386496,6.0.97.82

[IconGroups]
Group0=KeyBS
PrivateGroup0=-1
Parent0=$(Programs)

[KeyBS]
Icon1="KeyBS.exe"
Title1=KeyBS
StartIn1=$(AppPath)

[Setup]
Title=KeyBS
DefaultDir=$(ProgramFiles)\KeyBS
AppExe=KeyBS.exe
AppToUninstall=KeyBS.exe

[Setup1 Files]
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04
12:00:00 AM,152848,6.1.97.82
[email protected],$(WinSysPath),,$(Shared),6/18/98 12:00:00
AM,89360,6.0.81.69
[email protected],$(WinSysPathSysFile),,,6/13/00 12:00:00
AM,415504,3.51.2404.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/27/04
5:08:01
PM,262144,3.51.623.0
[email protected],$(WinSysPathSysFile),,,1/10/04 7:37:02
AM,380957,6.0.72.9589
[email protected],$(WinSysPathSysFile),,,3/16/04 2:44:16
PM,30749,6.0.1.9431
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,139264,3.51.623.0
[email protected],$(WinSysPathSysFile),,,8/27/04 5:08:01
PM,36864,3.51.623.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,6/13/00
12:00:00
AM,1046288,3.51.2723.0
[email protected],$(MSDAOPath),$(DLLSelfRegister),$(Shared),4/27/98
12:00:00 AM,570128,3.51.1608.0
[email protected],$(MSDAOPath),$(TLBRegister),$(Shared),5/15/98 12:00:00
AM,73184,0.0.0.0
[email protected],$(WinSysPath),,$(Shared),7/11/97 12:00:00
AM,311296,8.0.0.3512
[email protected],$(AppPath),,,10/1/04 5:04:19 PM,188416,2.0.0.0

; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top