Re: Feature is not available?

Tech-Archive recommends: Speed Up your PC by fixing your registry



Sorry but I'm not following you. I do have FoxPro 6 installed but that
shouldn't matter one way or the other if I'm simply using the oledb driver to
access a table. And as I mentioned earlier, I am using the same connection
string as the web app.

As for 'code in the database', I'm dealing with FoxPro 6 free tables, DBFs.
I don't think that applies.

Also I've checked and all users of this computer have complete access to and
control of the directory where the tables are located.

"Paul Pedersen" wrote:

Typically that message will appear if you try to do something that's not
allowed in the runtime version (i.e., FoxPro is not installed on the
machine). Older Foxpro's like 6 were more picky about that than 9.

Is it possibly due to some code in the database? I forget what all the
forbidden features are/were, but some are: DEBUG, COMPILE, SET STEP ON,
things like that. If there are such commands in the db procedures that
automatically run on open, you might get that message.





"B. Chernick" <BChernick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D563964D-7253-4834-B6BC-0022A3DB154D@xxxxxxxxxxxxxxxx
On dc.open. Here's the actual code. sConnStr is the connection string
described earlier.

Dim dc As New OleDb.OleDbConnection(sConnStr)
Try
dc.Open()
Catch ex As Exception
MsgBox("Open Fails, error = " + ex.Message)
Exit Sub
End Try

"Paul Pedersen" wrote:

What is the line that's causing the error?


"B. Chernick" <BChernick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14E43ECC-8BEB-4B8D-8AA4-21C23A550614@xxxxxxxxxxxxxxxx
I'm trying to write a quickie Winforms utility (VB, 2.0) that will pack
some
FoxPro 6 dbf tables. Unfortunately the same connection strings that
worked
with my web app don't seem to work in Winforms. It's crashing on open
with a
'Feature is not available' message. (And yes I've already checked
ConnectionStrings.com)

I've tried a connection string of both:
"Provider=VFPOLEDB.1;" + <file path> + ";Collating Sequence=General"
(This is what I've been using in my web apps.)
and

"Provider=VFPOLEDB.1;DRIVER={Microsoft Visual FoxPro
Driver};SourceType=DBF;" + <file path> +
";Exclusive=NO;BackGroundFetch=NO;NULL=NO;Collate=MACHINE"

(got that one from ConnectionStrings.com)

What am I missing?

(Is there some reference I'm forgetting? Something extra needed in
Winforms
but not web apps???)






.



Relevant Pages

  • Re: Feature is not available?
    ... Microsoft Visual FoxPro MVP ... Unfortunately the same connection strings that ... with my web app don't seem to work in Winforms. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: FoxPro 6 security question
    ... There is no security whatsoever on VFP dbf files themselves. ... web app that uses some FoxPro6 dbf tables. ... that FoxPro tables in themselves have very little buildin security. ...
    (microsoft.public.fox.programmer.exchange)
  • Is this possible?
    ... We have a temporary Dot Net 2.0 web app that connects to some FoxPro 6 DBF ... button on the main page to run a Pack command. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Feature is not available?
    ... Is it even possible to do a 'Pack' outside of FoxPro 6 itself? ... with my web app don't seem to work in Winforms. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Feature is not available?
    ... FoxPro 6 dbf tables. ... Unfortunately the same connection strings that ... with my web app don't seem to work in Winforms. ...
    (microsoft.public.fox.programmer.exchange)