Recent content by SLamb88

Thanks, we've got it figured out. Buried in the stored procedure is a reference to a second DB that he didn't have access to.

I have a user who gets the following error when running a report against a SYBASE database: Error in File D:\Program Files\Business Objects\BusinessObjects Enterprise 11\Data\procSched\srgd1505.reportjobserver\~tmp13a457247eaa0341.rpt: Failed to retrieve data from the database. Details...

We have a development database with sensitive data on it that we would like to mask. I've done so with a translate statement, but the problem is, the key is in the script, so anyone with access to the script could decipher the masked data. We have a similar process in SQL server that randomly...

That got it working. Thanks, Steve

I have a program, written in VB6 that allows the user to edit the incoming .CSV file using MS Excel. It does this by executing the following sub when a button is clicked: (sFile is the name of the file to be edited) Private Sub Excel_Edit(sFile As String) Dim objExcel As Excel.Application...

Here's another from the department of redundancy and repetition: My personal favorite, from the menu of the executive dining room at my company is "with aujus". SLamb88

I have a program coded in VB 6.0, and when the user clicks on a button, it opens up a document in word, the code in the click event looks like this: Dim objWord As Word.Application Dim strMessage As String Dim intResult As Integer If bFileExists(gStrText) Then Set objWord = New...

Thanks for the info. I checked all the security rights and everything looks good, but jsut to be sure I logged onto the machine locally as "Administrator" and it still blew up. However, I now think it's something with my machine, because it ran fine on another. This may be something...

I just wrote a rather simple VB 6.0 program, and created a package using Visual Studio's Package and Deployment Wizard. Everything appears to have gone fine. However, when I run setup.exe, I get the message that: The instructions at "0x00000000" referenced memory at...