DAO Workspace Database Collection (1 Viewer)

[GPGeorge]

The_Doc_Man:

So now I have a decision to make, stay with ACCESS or go with a new Db.


One Hopes for that. I always try and get things to work first, then optimize for speed.

---------------------- FWIW-----------------------
Data files originally started out as flat files.
When "Revelation" Db came out I moved to that.
"Revelation" disappeared,
DB3, I think bought it, and PARADOX came on line around the same time.
So I moved everything to PARADOX, and then ported over to ACCESS after that.
One thing I've always disliked about ACCESS -- in my situation -- is I need to build a separate query for each Symbol.
ACCESS won't allow variables in "stored" queries for whatever reason. Just remembered this issue.
Going to a new Db may solve that issue..
--------------- FWIW End ----------------------------------

Actually, I'm not sure we have enough information to respond adequately to some of these statements. Specifically, the reference to variables in queries.

What you are probably missing are parameterized queries. Many queries can be parameterized with form references, for example, as well as with TempVars and even VBA functions.

The following statement reveals a lot about the shortcomings of the current approach, unfortunately.

"All forms, reports, and anything else is handled outside of Access by Creating/Updating ACCESS tables or by executing one of the queries."

Given that forms and reports are Access objects, and given that those objects exist ONLY inside an Access database, this statement begs further explanation. What are you calling "forms and reports?" How do you produce them? How do you use them? Thank you.

 

[dw85745]

NauticalGent: Thanks for responding.
Link: (for some reason forums will not accept a link).

Will have to play with it to see if can be accessed from Code other than Access VBA..
If it can be used in stored procedure, this would greatly reduce the number of stored procedures I use.
In compiled code - objects are either early or late bound. Early bound gives a performance boost.
How ACCESS deals with stored procedure I'm Not sure.
M$ link say TempVar(s) are objects.
From my read they appear to be a global variable collection (text and numbers only)

To use them several questions arise.
1) Are stored procedures considered an object? If so, are they early bound?
2) If a TempVar(s) is used in that stored procedure does it change to latebound?

 

[NauticalGent]

@dw85745 , give this a read: https://www.devhut.net/access-tempvars/

 

[Gasman]

Link: (for some reason forums will not accept a link).

You need a few more posts before you can post an actual link.
You can break it up with spaces.

 

[cheekybuddha]

You need a few lot more posts before you can post an actual link.

There, FTFY!

(Currently I think the post count required before being able to post links is 100)

 

[Gasman]

There, FTFY!

(Currently I think the post count required before being able to post links is 100)

It is, but I did not want to dishearten them.

 

[cheekybuddha]