×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Working with SQL

Working with SQL

Working with SQL

(OP)
Well I am not sure which forum is best to post this in, if I have it wrong please move this post.

For years I have been working with a hybrid of Access, an online data base and csv imports. Two years ago I embarked on a journey to build a SQL backend and to get this accessible by clients in real time as we move about their sites doing our work. This is partly complete...however I am now at the point where I can see an end to the tunnel so to speak. To take the next step is to move away from the old online database and csv imports however to do this a lot of things change at once. I am telling this for context and background.

To make this move I am having to rebuild the office end of the chain first. This consists of an Access front end with a smattering of local tables to link to the SQL server online.

I already am aware of limiting fields and restricting records to reduce server traffic. However I was wondering what others approach may be to queries and loading subforms (which seems to take forever) when working in this manner?

RE: Working with SQL

We have been using various Access databases with a MS-SQL back end for a number of years. If the indexes on the tables are set up correctly, we normally do not have any issues. Not sure why you need local tables to link to the SQL server, but then again I am not a full time Access DB developer. Fortunately we have a very robust network at our organization, so network slowness normally is not an issue unless we use the wireless (and a lot of users are on the wireless also).

RE: Working with SQL

"I already am aware of limiting fields and restricting records to reduce server traffic. However I was wondering what others approach may be to queries and loading subforms (which seems to take forever) when working in this manner?"

You definitely want the fields linking a form and subform to be indexed fields within the tables.

Also, if you are running queries against the SQL Server db, you want all the fields in the JOIN, WHERE and ORDER BY clauses to be indexed fields.

Brooks

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close