Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.basic.visual.misc > #1703

Re: ADO Problem in VB 2010

Show all headers | View raw

>
> "Jason Bodine" <jbodine1974@gmail.com> wrote in message 
> news:79d24a1f-b9fb-4d88-8717-4889fae955a7@googlegroups.com...
> Hi,
>
> Well, aside from the fact that *every single tutorial* when I type ADO.NET 
> into Google uses the COM objects and uses the very type of code I posted 
> here (and somehow it works for *them*, lol), the problem with using 
> ADO.NET is that it's a lot
> more complicated than I'm used to.  I am a Classic VB veteran, and in fact 
> the application that I'm working on converting was originally written in 
> VB6.  Only reason I'm trying to port it over to 2010 is I need the added 
> functionality of *that* language
>  to apply some of the more major updates I have in mind for this version 
> of the application.  The database part, while vital its operation, doesn't 
> need all that added hooplah.  It just needs to be able to create the 
> database and then store to and retrieve
>  information from it.
>
> Besides that, the people on this group have always been a lot more helpful 
> than some of the others!  I've come across some pretty elitist programmers 
> before who seem to think if you don't already know what you're doing with 
> whatever language they
> program in, then it's not worth their time to teach you.
>
> Anyway, thanks for responding!  I guess I'll keep looking and hope I can 
> find *something* that works!
>
> Jason

Hi Jason,

This may not be relevant, but I recently encountered a problem with 
connection strings in VB6 which was due to a change in Microsoft's security 
policies. The change caused previously valid connection strings to no longer 
work because security related content was removed from the connection string 
that the ADO object returned. User name and password I could understand, but 
so much of the string was removed that saving it so that the user could 
reconnect easily the next time they used the program just didn't work.

The solution in my case was to add a flag to force the return of a usable 
connection string by using the code:

  MyADODB.Properties("Persist Security Info") = True

before doing the connection the first time (when the user manually selects 
the required database) and then getting the connection string using the 
code:

    ConnectionString = MyADODB.Properties("Extended Properties").Value

The returned connection string then worked fine.

You could try using ADO to connect to an existing MDB file and then copy the 
complete connection string with the new database name to see if that works 
to allow you to add the tables you require. Once you get a working string, 
you can then try trimming out components to get a minimal set that works.

Good luck!

John

Back to comp.lang.basic.visual.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ADO Problem in VB 2010 Jason Bodine <jbodine1974@gmail.com> - 2013-01-20 23:20 -0800
  Re: ADO Problem in VB 2010 Jason Bodine <jbodine1974@gmail.com> - 2013-01-21 09:16 -0800
  Re: ADO Problem in VB 2010 Jim Mack <no-uce-ube@mdxi.com> - 2013-01-21 12:28 -0500
  Re: ADO Problem in VB 2010 Deanna Earley <dee.earley@icode.co.uk> - 2013-01-21 17:36 +0000
  Re: ADO Problem in VB 2010 "Mayayana" <mayayana@invalid.nospam> - 2013-01-21 12:47 -0500
    Re: ADO Problem in VB 2010 Jason Bodine <jbodine1974@gmail.com> - 2013-01-21 22:07 -0800
      Re: ADO Problem in VB 2010 "John Paine" <john.paine@bigpond.com> - 2013-01-22 18:32 +1030
      Re: ADO Problem in VB 2010 Deanna Earley <dee.earley@icode.co.uk> - 2013-01-22 09:23 +0000
      Re: ADO Problem in VB 2010 ralph <nt_consulting@yahoo.com> - 2013-01-22 08:15 -0600
        Re: ADO Problem in VB 2010 ralph <nt_consulting@yahoo.com> - 2013-01-22 10:38 -0600

csiph-web