Search results for query: *

Thanks BobWman, that was exactly right.

OK, I tried putting my app on a different machine and it worked fine there no matter what user I logged on as. I also tried running it from the VB IDE on my machine logged on with a multi-user account and as soon as I opened up the VB IDE, I got the installer trying to install Office 2000. So...

That makes some sense, and I could just let it install what it wants. The problem is that most of our plant is standardized on Office 97 and for the PC's that will be running this app, we don't want to have to install, nor do we have licenses for, Office 2000. I still don't understand why...

I can't delete it. When I said icon, i didn't mean shortcut. It's just the executable or project file. I don't think that has anything to do with it. It doesn't matter how I run it. Thanks anyway though. Anyone else have ideas?

I was launching it from the icon. Either the .exe or the .vbp file. Same problem. But I didn't install anything. It's just a vb project. I built this app on my machine and all I did was make the .exe file. And when I open it on my machine logged in as myself it's fine. When I open it on...

No, it's on my own dev machine. I'm not using the installer. It just popped up. Here's why I needed to test this: Sometimes users will be using this app from their own machine, and sometimes it will be on a shared machine that is logged in with a multi-user domain account. I need to check...

Hi, I am working on a standard VB6 project. I am running windows 2000 and have no problems when I am logged on as myself. When I log on to my machine with a different domain account and try to open the VB project or run the VB executable, the windows installer pops up and tries to install...

I'm not sure if this is the right forum. We have a SQL Server 2000 database that we need to access from an ASP.Net page running on a separate server. I would like to be able to use windows authentication so users will not have to enter a username and password on the web page. Is it possible...

Either I'm a little confused or WildHare is. You're not using that code as a unique identifier for members are you? If not, I would definitely split them into separate fields. They each have separate meanings and should never have been put in the same field. That's like putting someone's...

Please don't do that. Create another table. This will make it simpler, faster, and more flexible for everything you do in the future. Trust me.

I would not recommend windows 98. By SQL, they probably mean SQL Server. It's good, but expensive and may be overkill. Microsoft Access works fine in a network environment if you don't have many concurrent users. I would say with anything less than 10 it would work fine. What about Visual...

One option is to create a form for printing. Put images, labels and textboxes on it. Then you can set all the textbox values and do a frm.PrintForm to print it out.

It looks like you may be able to use the CommonDialog control and set it's PrinterDefault property to false. Look up the PrinterDefault property in the MSDN.

Here's what I use: Sub PrintStuff(strPrinter as String) Dim prn As Printer For Each prn In Printers If UCase(prn.DeviceName) = UCase(strPrinter) Then Set Printer = prn Exit For End If Next frmWhatever.PrintForm End Sub It doesn't change the default windows printer...

Craig, First, you should NEVER have a field named "Date". Of course, sometimes it's already done and your stuck with it. Same goes for field names with spaces. But you can just use brackets: rs![Date] rs![Batch Number] I always use rs!FieldName. I find it easier to read and I like...

Yes, the standard GetUserName works fine for me in win 2K Here is the code I use: Public Declare Function GetUserName Lib "advapi32.dll" Alias "GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long Public Function GetUserLogon() As String ' Display the name of...

Tlbroadbent, that's exactly what the problem was. My 8000 character strings were correctly defined as varchar not nvarchar. But I was using an nvarchar as one of the variables that went into building the 8000 character string. Declaring everything as varchar solved the problem. It seems to...

I found the problem. In the strings that I was building, even though the string variable was a varchar, I was using nvarchar variables to build the string and I think this was taking up extra space and getting truncated. I changed everything to varchar and it works now.

I am using several varchar variables in a proc to dynamically build a long string then execute the string with exec. EXEC (@string1 + @string2 + @string3) When I limit the size of each string to 4000 it works fine. If I let it go to 8000 it fails. The errors indicate the strings are being...

Thanks for the input. I actually just turned 30. I spent about 6 or 7 years going to school part time and got a BS in General Science. That was pretty useless, so I went back and spent 2 full-time years getting my CS degree. I was just offered a permanent position today with the company I...