?
Solved

Error 380: Invalid Property on Windows Server 2003

Posted on 2006-11-24
5
Medium Priority
?
154 Views
Last Modified: 2013-11-26
Hi Everybody!

Currently I'm programing an Interface kind of program that works fine on every OS I test it, but when it comes to Windows Server 2003 I get the 380: Invalid Property Error.

The wierd thing is that according to my debugging logs, the error occurs at a line that checks if a recordset is at EOF.

I'm using the following parameters:

    My machine:
        - OS: Windows XP Professional
        - IDE: Visual Basic 6.0 SP6

    Target Computer:
        - OS: Windows Server 2003 Standard
        - Database: Microsoft SQL Server 2000 SP4

    Code:
        - Database Control: DB1: Adodc
        - Connection String: "Provider=sqloledb;Data Source=localhost;Initial Catalog=MyDB;User Id=Me;Password=Me;"
       
        - Code Extract:
                    'Load Parameters (OK)
                    'Display Forms and Controls (OK)
                    'Get Files via FTP (OK)
                    DB1.Recordsource="Select * From MyTable;"
                    DB1.Refresh
                    If DB1.Recordset.EOF then
                        MsgBox("No Records.")
                    End If

When the program gets to the If line, I get the 380: Invalid Property Error.

I don't have Visual Basic IDE installed on the Target machine, but that's the last thing I want to do, only if nothing else works...

Any help will be very appreciated!! Thanks in advance.
0
Comment
Question by:smaldona
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 9

Expert Comment

by:pradapkumar
ID: 18007134
 DB1.Recordsource="Select * From MyTable;"
                    DB1.Refresh
                    If DB1.EOF then
                        MsgBox("No Records.")
                    End If

try the above one.
0
 

Author Comment

by:smaldona
ID: 18010102
Finally got it myself... after a full day of debugging I found out I mistyped a proerty value when logging to the Event Viewer, and I didn't set the Explicit Option...

Sorry to bother you all...

Thanks anyway!!
0
 
LVL 1

Accepted Solution

by:
DarthMod earned 0 total points
ID: 18449450
PAQed with points refunded (125)

DarthMod
Community Support Moderator
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are many ways to remove duplicate entries in an SQL or Access database. Most make you temporarily insert an ID field, make a temp table and copy data back and forth, and/or are slow. Here is an easy way in VB6 using ADO to remove duplicate row…
Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question