Compiling VB6 DLLs in Vista

Visual Basic

    Sponsored Links

    Next

  • 1. MSHFlexGrid Problem (cell colors not staying!)
    Hi Group Using VB6 latest SP. Ive got a MSH FlexGrid bound to a Datasource (a recordset) Ive got an option of showing only those records that are highlighted This requires a trip to the database to look for values that would be highlighted if shown on the grid. I set Redraw to FALSE (fg.Redraw = False) then I bind the chosen recordset to the grid, row by row, i color the cells the highlighted color. For i = 1 to fg.rows - 1 for x = 1 to fg.cols - 1 fg.cellbackground = HighlightedColor 'defined elsewher next next I set Redraw to TRUE This works fine. But,it doesnt work when I try Sorting the recordset: Redraw = False put the grids datasource into an ado recordset variable: set rs = fg.datasource Sort the recordset: rs.sort = "fielda = 'one' AND fieldb = '2'" Rebind the recordset to the grid: fg.datasource = rs Color the cells: for i = 1 to fg.rows - 1; (see previous) Redraw = True Whats weird is, when I step through it< it works! But, when I run the sort operation (without stepping through), it doesnt work. am I using the Redraw incorrectly or something? TIA, Eric
  • 2. EAN128 OCX
    Seek OCX for printing BARCODE EAN128. Can somebody point me a download site? Thx Gard.
  • 3. msvcrt.dll error please help !!!!!!!!!!
    Hi , I am using CDO1.21 and VB to create appointments. Suddenly my code has started giving error "Method Update of object AppointmentItem Failed" After that another error comes as "Instruction at xxxxxxxxxxxxx requested memory at xxxxxxxxxxxxxxx. Memory could not be read. Click OK to Abort or Cancel to Debug. " On Debugging I found the error is in File Msvcrt.dll . My version of this file at c:\windows\system32 is 7.0.2600.1106 . Can somebody please help me. I am using Windows XP. The same code was running perfectly fine for the last 3 months. Please help me.... Regards, Akil.
  • 4. Common Dialog Control ShowPrinter Method and The Printer Object
    I'm trying to use the Common Dialog Showprinter method to select different printers from the printer collection, but I'm printing using the printer object to print with.. How do I pass the selected printer from the Common Dialog Control to the Printer Object? Any and all help is greatly appreciated. Please help me! -Carl
  • 5. How many certificates?
    I have been doing some cursory research on this, but as of yet I have been unable to find the one piece of information that would answer my question: If our shop is developing using .NET and VBA, how many code signing certificates do we need? Do we need one for VBA (Office 2003) and one for VB.NET? Will ONE authenticode certificate sufice? Thanks, Ricardo Parodi

Re: Compiling VB6 DLLs in Vista

Postby Ralph » Sun, 10 Sep 2006 22:33:28 GMT






Here is probably as good a place as any (while theoretically ~.vb.com is the
more appropriate site). This group and ~.vb.general.discussion have perhaps
the most activity.

So what did M$ break this time? <g>

-ralph



Compiling VB6 DLLs in Vista

Postby Garry » Sun, 10 Sep 2006 23:16:16 GMT

Which newsgroup shud I use to ask questions about Vista and problems 
compiling VB6 DLLs there????? 



Re: Compiling VB6 DLLs in Vista

Postby Ralph » Sun, 10 Sep 2006 23:25:32 GMT





installed
version
another
<snipped>

If I understand you correctly, then yes these areas are now off-limits by
default. The idea is to eventually deny all access to 'special folders'
except thru a specific 'install/gatekeeper'. Admin alone doesn't always
carry the weight it once did. <g> Which leads to strange situations like
yours.

There are numerous subtle changes to permission and ownership rules in
Vista. I will not pretend to understand them at this time. Also be aware, as
I am sure you are, that Vista is still beta. It is difficult at times to
determine if is 'Me', their feature, or their bug. <g>

You can over-ride the behavior you are seeing, but IMHO it is better if you
compile to another folder and then 'install' the file to where you want it.
After all you might as well get used to it as it is only going to get worse.
<g>

-ralph



Re: Compiling VB6 DLLs in Vista

Postby Garry » Sun, 10 Sep 2006 23:42:32 GMT

Well, I compile directly to c:\ProgramFiles\Common 
Files\CompanyName\MyDLL.dll and use this as the source for my Wise script.
I installed the very latest version of Vista on my second machine, installed 
VB6, updated all the third party components and installed the latest version 
of my apps, using setups I generated from Wise scripts, to equalise the 
Vista machine with my production machine. (Win XP SP2 and very much up to 
date).

When I tried to compile a DLL, I got a standard message that I dont have 
permission. And a string with the target file name. I can compile to another 
folder but nothing in c:\Program Files\etc etc etc

Am I doing something wrong. Obviously I have administrator permissions.

Kudnt find Outlook Express there too so I am contacting you from my 
production machine.

Vista can be very very frustrating to an experienced user of XP 'cos some 
things are missing completely OR in different places. I feel old..













Re: Compiling VB6 DLLs in Vista

Postby Garry » Mon, 11 Sep 2006 00:33:40 GMT

Yes. I imagined that was the direction that MS was going BUT, I thought that 
I was working according to Microsoft Best Practices as I used to compile 
directly to the Sys32 folder. Sometimes Microsoft is never satisfied.



Thanks for the replys

Garry













Re: Compiling VB6 DLLs in Vista

Postby Ralph » Mon, 11 Sep 2006 01:17:25 GMT





that
<snipped>

To be strickly accurate I should emphasize that is my best guess as to what
is going on. We have seen the behavior, but lack any 'official'
pronouncement.

Getting complete answers from M$ about Classic VB and COM is not easy. It
puts me in mind of the old days of the Oracle/M$ 'wars'. If you called
either support line and mentioned the other - all you got was immediate
silence. <g>

So for the future, your best bet with any issue is to try and duplicate the
behavior with a non-VB app or COM component, and then ask about it. <g>

-ralph



Re: Compiling VB6 DLLs in Vista

Postby Michael C » Mon, 11 Sep 2006 17:13:16 GMT





Just trying to create a txt file in prog files should determine that it is 
not a vb issue.




Re: Compiling VB6 DLLs in Vista

Postby Garry » Tue, 12 Sep 2006 00:12:15 GMT

Well yes, it is not directly a vb6 issue but it is very pertinent to those 
who wish to continue to compile VB6 DLLs.













Re: Compiling VB6 DLLs in Vista

Postby Karl E. Peterson » Wed, 13 Sep 2006 05:52:13 GMT



If you compile to your own profile, you're set.  Otherwise, MS considers you
to be a very bad boy indeed.  Here's some further reading:

 http://www.**--****.com/ +%22user+protection%22
-- 
Working without a .NET?
 http://www.**--****.com/ 



Re: Compiling VB6 DLLs in Vista

Postby Garry » Wed, 13 Sep 2006 14:52:02 GMT

Well, the response has to be rather lengthy.
We iz two programmers working on various projects in VB6 so we have to 
compile DLLs to a common folder. That leaves out a named user folder.
We need the folder to be on a destination machine AND locked to the end 
user.
The %Program Files%\Common Files\CompanyName folder was ideal for this as 
the end user, if using the Windows Explorer was warned before having the 
contents of Program Files being displayed to him in XP assuming he was an 
Admin. If he was a Limited User, he couldn't change anything in Program 
Files anyway..
If it is locked to him in Vista, even as an Administrator, as many home 
users will be, so much the better. But WE need the Common Files\CompanyName 
folder on our production machines to be 'open' to insert newly compilled 
DLLs and as source file DLLs in Wise Script..
The solution offered here to 'open' the Common Files\CompanyName satisfyes 
our requirements without compromising the end user's machine. That is, I 
think, wot Microsoft intended.












Re: Compiling VB6 DLLs in Vista

Postby Karl E. Peterson » Thu, 14 Sep 2006 02:07:08 GMT



Personally, I often take the *inverse* of Microsoft's "recommendatations" to
be "best practice."  This notion of only being able to write to your own
profile, while it may make sense for the kid running the cash register, is
ludicrous for actual knowledge workers.
-- 
Working without a .NET?
 http://www.**--****.com/ 












Re: Compiling VB6 DLLs in Vista

Postby Ralph » Thu, 14 Sep 2006 02:33:58 GMT







to
<snipped>

If you think that is fun wait until you try to write drivers and/or debug
services on YOUR OWN DAMN BOX!

I know this is silly, but I wouldn't be surprised that Vista will be
Released in three versions: Home, Professional, and for another hundred
dollars - a developer's edition. <g>

Or perhaps a MSDN subscription will become manditory.

-ralph



Re: Compiling VB6 DLLs in Vista

Postby Ken Halter » Thu, 14 Sep 2006 04:22:39 GMT






"Microsoft Best Practices" should be "Microsoft Best Practices for today"

fwiw, I compile directly into the folder that contains the source. 
Afterwards, I copy the new component to a release folder.

imo, the Sys32 folder and the registry should remain as clean as you can 
possibly keep them. I've never seen Vista installed anywhere so I haven't 
got a clue about it's quirks. I do know that anything from Microsoft that's 
labelled BETA, will not be installed on any PC I care about. Their RTM 
versions are scary enough these days with their "release it, get bug reports 
from poor, unsuspecting users, ignore those reports while working on the 
next cash cow" policies they seem to have these days. Everyone and 
everything at Microsoft is disposable these days, it seems. (do I seem 
bitter? <g>)

-- 
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory -  http://www.**--****.com/ 



Re: Compiling VB6 DLLs in Vista

Postby Garry » Thu, 14 Sep 2006 16:43:55 GMT

I agree.

And Microsoft haz provided two possibilities as explained to me in the above 
answers.

a)    Make the target Folder %Program Files%\Common Files\CompanyName 
accessable for read/write by an Admin user on my production machine. I am 
the only user.

b)    Enable VB6.exe to 'Admin enabled' and it will then be able to write to 
the %Program Files%\Common Files\CompanyName  folder without me changing the 
write permissions for that folder.

And, I agree with Microsoft. I may have had to learn something by writing to 
these newsgroups, but the basic Microsoft permissions policy seems VERY 
SOUND to me.

The info on how to adjust the permissions may even be written in some 
obscure place in the help files where only Google will find it.

Garry


















Re: Compiling VB6 DLLs in Vista

Postby Ralph » Thu, 14 Sep 2006 21:55:29 GMT





above
to
the
to

While I definitely sounded like I was complaining about the new 'security' -
it was more the childish whining of a gerontoprogrammer who finds himself
annoyed by changes. It is uncomfortable, after all these years of being the
absolute Master of My Domain, to be suddenly faced with insubordination over
a request to perform a trivial task.

In the long run making the attack surfaces smaller by default is good thing.
But it sure is a PITA! <g>

-ralph



Similar Threads:

1.compiling VB6 on vista could not create reference comsvcs.dll

Hello,

I'm getting a could not create reference to comsvcs.dll when I try to
compile a vb6 COM+ component on my vista box.  I'm running the vb6 iis
as an admin.

I can compile the same component on my win xp pro box just fine.  I've
looked at both machines and I'm pretty sure all the references exist
on the Vista box.

Has anyone seen this?

-Eric

2.Compiling DLL & Vista: Follow up

Well, apparently if you make VB6.exe and Link.exe at always run as 
administrator, this will solve some of the problem.

What sucks is that I keep all my projects in their own folder, and Vista 
won't allow VB to write settings to the .vbp file.  Stupid Vista.  Too many 
workarounds.  :\


"Kevin Provance" < XXXX@XXXXX.COM > wrote in message 
news:% XXXX@XXXXX.COM ...
| This might have already been answered, but I cannot find it.
|
| Using VB6 SP6 under Vista.  I am logged on as an administrator.  When I
| attempt to compile an ActiveX DLL, I get the message "Error accessing 
system
| registry"
|
| When I try to register the same DLL I get an error 0x80004005
| DllRegisterServer failed (seems to be another registry access thing).  I
| knew this was going to be a PITA.
|
| Does anyone know what's up with this?  I'll continue to Google in the
| meantime, but there isn't a lot of info out there that I am able to find 
as
| of yet.
|
| Thanks guys
|
| - Kev
|
| 


3.Compiling DLL & Vista

This might have already been answered, but I cannot find it.

Using VB6 SP6 under Vista.  I am logged on as an administrator.  When I 
attempt to compile an ActiveX DLL, I get the message "Error accessing system 
registry"

When I try to register the same DLL I get an error 0x80004005 
DllRegisterServer failed (seems to be another registry access thing).  I 
knew this was going to be a PITA.

Does anyone know what's up with this?  I'll continue to Google in the 
meantime, but there isn't a lot of info out there that I am able to find as 
of yet.

Thanks guys

- Kev 


4.Can't compile using VB6 in Vista

Hi Im trying to compile my program in vista which previously compiles fine in 
Vista, however I am now not able to make my software as it tells me that VB6 
stopped working. It is currently faulting at iphlpapi.dll even though I've 
taken out the API's reference from my codes. I'm currently running as an 
administrator as well. I've also run the compatibility wizard on VB6. Has 
anyone encountered this problem or knows how to fix it?

Here's some details on the crash: 
problem even name: APPCRASH
app version: 6.0.97.82
fault module name: iphlpapi.dll
fault module version: 6.0.6000.16386
exception code: c0000005
exception offset:00006451

If anyone needs more detail please let me know.

Thanks in advance!!

5.Compiling VB6 Apps on Vista

6. Q: Compiling VB6 Apps on Vista

7. Does the VB6 CommonDialog work (compiled on Win98se) work on Vista

8. Vista and VB6 DLL



Return to Visual Basic

 

Who is online

Users browsing this forum: No registered users and 72 guest