Solved

Error 380: Invalid Property on Windows Server 2003

Posted on 2006-11-24
5
151 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

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

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…
Introduction While answering a recent question about filtering a custom class collection, I realized that this could be accomplished with very little code by using the ScriptControl (SC) library.  This article will introduce you to the SC library a…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…

690 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