Newsgroup: it.comp.lang.visual-basic
Titolo: BACO!!!! VB6 MSHFlexGrid

Casualmente (e per fortuna) ho scoperto che se, usando un controllo Griglia
MSHFlexGrid incluso in VB6, riempio la griglia con AddItem, la svuoto con i
RemoveItem, e la riempio nuovamente, mi salta le prime inserzioni (in realtà
ci sono, ma lui non le fa vedere a video), tanto che l'unico modo che ho
trovato per risolvere il problema e inserire una cinquantina di righe vuote
ed alla fine rimuovere tutte le righe vuote con un ciclo.
Soluzione che non mi sembra il massimo dell'eleganza.
Probabilmente ho solo settato qualche combinazione di proprietà che manda il
controllo in crisi, ma ho voluto mettere tutti al corrente del problema e se
qualcuno lo ha già riscontrato e risolto mi indichi come.
Se esiste un SP che risolve la cosa, per favore, ditemi dove trovarlo (o
inviatemelo, non ho idea di quanto possa essere ingombrante un SP)
Ciao.

Ciao.
CIAO
non ho idea se questo risolvera' il problema ma l' SP1 x VB6 lo trovi a
http://msdn.microsoft.com/vstudio/sp/default.asp
ciao ciao
marco

inviatemelo, non ho idea di quanto possa essere ingombrante un SP)
Ciao,
il Service Pack 1 puoi scaricarlo da :
http://msdn.microsoft.com/vstudio/sp/default.asp
esiste in 2 versioni ,
la CORE che é la versione di base e si ciuccia quasi 15MB
e la versione FULL che invece é di circa 43 MB
( una bazzeccola per un prodotto appena rilasciato :-))
io ho scaricato la versione CORE
(MS dice che se non si usa Visual C++ dovrebbe essere sufficiente questa)
P.S. aspettando un attimo dovrebbe essere disponibile su qualche rivista...
Per sapere cosa aggiorna ti allego il file readme.
Ciao
Roberto
----------------------------------------------------------------------------
------------------------------------------------------
Microsoft Visual Studio 6.0 Service Pack 1 Readme
The Microsoft® Visual Studio® 6.0 Service Pack 1 Readme (Core Version)
contains the following sections:
Overview
Installation
Notes on Fixes
Finding More Information
Overview
The Microsoft Visual Studio 6.0 Service Pack 1 addresses known binary
compatibility bugs with certain run-time redistributable files in Visual
Studio 6.0.
Before installing this Service Pack, shut down any Visual Studio
applications. Install this Service Pack whenever you have updated or changed
any of the applications in Visual Studio to ensure that you have the latest
fixes.
Installation
From the root directory of the Service Pack, run Setup.
Determining the Files That Setup Installs
Setup might not install all the files included in this Service Pack on your
computer. If a file on your computer is a more recent version than the one
in the Service Pack, Setup will not update the file on your computer.
Updating Files You Previously Modified
The primary way Setup determines which files to replace is by checking the
version information in a file's resources. However, some files, such as text
files and nonbinary files, have no resource information. In these cases,
Setup uses the time stamp to determine which files need to be replaced.
If you have altered the time stamp on any of the Visual Studio component
text files or files that do not have version information, then Setup may not
replace those files. Source files and header files are examples of some
files you may have changed.
Determining the Update History of the Products Based on File Versions
To determine which updates have been made since the initial release of a
product, you will need to examine the version number in the properties of
one or more files.
To determine the update status of a product:
1. Look in the table below to determine which file you want to examine. In
some cases, you may need to examine more than one file to determine fully
the product's update history.
2. For each file, right-click the file in Windows® Explorer, then click
Properties.
3. Click the Versions tab, and compare the version listed with the version
in the table.
The following table lists the developer tools that have been updated in this
Visual Studio 6.0 Service Pack. It also lists the key files you should check
to ascertain version information.
                                                           Version on
Product   Files                 Release       SP1
----------------------------------------------------------------------------
-------------------------
Visual Studio 6.0 oleaut32.dll 2.30.4261 2.30.4265
   olepro32.dll 5.00.4261 5.00.4265
   asycfilt.dll 2.30.4261 2.30.4265
   stdole2.tlb 2.30.4261 2.30.4265
Visual Basic® 6.0 msvbvm60.dll 6.00.8176 6.00.8268
Visual C++® 6.0   mfc42.dll 6.00.8168.0 6.00.8267.0
   mfc42u.dll 6.00.8168.0 6.00.8267.0
   msvcrt.dll 6.00.8168.0 6.00.8267.0
Visual J++™ 6.0 msjavx86.exe 5.00.2922 5.00.2925
   classd.exe 5.00.2922 5.00.2925
   classr.exe 5.00.2922 5.00.2925
Uninstalling the Visual Studio 6.0 Service Pack
The Service Pack cannot be uninstalled independently of Visual Studio. To
uninstall the Service Pack updates to a Visual Studio 6.0 tool, such as
Visual C++, you must uninstall the tool. The Service Pack updates will be
uninstalled with it. Then, reinstall the tools without the updates.
Notes on Fixes
Fixed Visual C++ Issues
The following Visual C++ issues have been fixed with this Service Pack.
Installing Visual C++ 6.0 caused problems with other applications built with
earlier versions of MFC.
CDialog::Create did not return FALSE when dialog creation failed.
MFC did not call CPrintDlg::OnInitDialog.
Inappropriate assertions were raised in debug builds in some Automation
routing situations involving nested activations.
ActiveX® controls that resize themselves in response to being moved would
cause a stack overflow.
Deserializing an ANSI string in a UNICODE release build of MFC would cause
an access violation.
In a multithreaded application, one thread calling setlocale( ) while
another thread was executing strftime( ) could result in an Access Violation
exception.
Fixed Visual Basic Issue
The following Microsoft Visual Basic issue has been fixed with this Service
Pack.
A run-time error can occur in compiled Visual Basic code when the
application uses more than eight in-process COM DLLs.
If your applications download run-time components from the Web on setup,
note that the following files have changed with this Service Pack:
msvbvm60.cab
vbrun60.cab
oleaut.cab
Fixed Automation Issues
The following run-time issue has been fixed with this Service Pack.
Passing in an unallocated array for an out-only SAFEARRAY parameter to a
late-bound method call will fail.
Updated Visual J++ Files
In response to the Automation issues, noted above, the Microsoft virtual
machine files were rebuilt. This change will be applied both on the machine
where Visual J++ is installed, and also to the Visual J++ redistributable
folder, so that Visual J++ applications that are distributed will also
include the updated Automation files.
To install and use the updated versions of the core VM class files, run
classd.exe or classr.exe.
Finding More Information
For more in-depth information about the Visual Studio issues that are fixed
in this Service Pack, see the Microsoft Knowledge Base articles available at
http://support.microsoft.com/support
.
To build a Visual Studio Service Pack query:
1. Choose "Any Products" from the list.
2. Click on more search options to get choices about how you will search.
3. Set the search type to "Keyword or Boolean search."
4. Enter one of the following as your search phrase:
For Visual Studio articles, enter kbvs600sp1fix
For Visual C articles, enter kbvc600sp1fix
For Visual Basic articles, enter kbvbp600sp1fix
5. Click "Find."
For the latest product information, see the Visual Studio Web site at
http://msdn.microsoft.com/vstudio
.