Access, SQL and VB

[EscapeUK]

I have a VB app (uses MTS) which saves data to a SQL DB with no problems at all. However when I run a long MS access Query against the DB and try to save using my VB app the VB app bombs out.

Seems to be a problem in running the MS Access (uses SQL ODBC connetion) and the VB app at the same time. I guess people must do this all the time.

Any ideas

 

[MichaelRed]

You don't need to run Ms. Access to manipulate the tables (or to run queries). The process of running VB, MS. Access and SQL DB may be overwhelming your resources. Try just running the query code from VB directly.



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[EscapeUK]

sorry i did not make this clear. I am running access completley from the VB app becuase thats what they want. The only thing they have in common is using the same SQL database

 

[MichaelRed]

Clear? What's Clear? I'm not Clear!

When I say "running Access", i refer to an actual instantiation of the program, as in app.activate. Is this what you are refering to? If you are just declaring the database and tables, you are not 'running access', but are running the Jet db engine for the 'information' retrievial purpose. If you are just using the Jet db engine, then the process does seem to be a bit off for accessing an SQL db, but then many 'customers' seem to be a 'bit off' to me.

The net result - to your customer and end user - would appear to be increased resource requirements (e.g. Faster processor and more memory) along with decreased performance (more delay in getting results - despite the increased resources).

I think, therefore I do not know. Could you draw a picture?
What functionality does Ms. Access provide to the overall app/process?


MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over