Search results

In your design master, just check the Replicable checkbox in the properties for each of the unreplicated tables, then synch with the other replica. Options for unreplicating that are easier than what you mentioned are outlined in the Jet Replication Wiki FAQ, Question #10...

The scripting runtime can be used with late binding, so no need for a reference at all. In the code given, you'd just comment out the variable declaration for fsoEarly.

The least complicated explanation of this is: 1. OrderByOn and FilterOn are being set in code at runtime, or by the user. 2. you have a CLOSE command button that is set to prompt for changes, i.e.,: DoCmd.Close acForm, Me.Name, acSavePrompt If you're using that code, you should change...

This is wrong. Dirty records never generate a prompt by default (only if you've programmed one). This prompt only occurs with a design change to the form. If there is any code that alters the form in design mode, or modifies sort order or the form's filter, then perhaps that's causing the...

Splitting and then sharing the front end is almost a waste of time. It gets you almost none of the benefits of splitting, while retaining almost all of the problems of running unsplit. Each user should have an individual copy of the front end. Updates to the front end should never be...

I hope you mean NOT a solution, since it's not. There is no necessity of using replication just because you have simultaneous users. Is the app split into front end (forms/reports/queries/etc.) and back end (data tables only)? If not, that may be one of the things making you think you need...

Replication should NEVER be used as a solution to performance problems. That's not what it's for, and you're just moving the problem without actually solving. You've also mis-identified the problem -- replication might be a solution when the problem is contention for locks on the data file, but...

If you need replication, then you need to recover the Design Master. This is a choice on the replication menu in the Access UI. But, it does show that somebody was incompetent and never bothered to understand how Jet replication works. Each replica in a replica set has a unique ReplicationID...

Installing, configuring and maintaining Jet indirect replication requires a lot of care and attention. It's similar to user-level security in terms of complexity of concepts, but much more complicated to implement (without Replication Manager, there are no wizards to walk you through it). It's a...

My guess is that Google is using dictionaries to match all word forms and Bayesian webs of relationships to cross-connect, say, mis-spellings with the desired results. I wouldn't know how to even begin implementing either of these things in Access. Nobody but Google has access to so much data...

You can speed up an Access app over a slow connection only so much. Using unbound forms will be faster but will require a huge amount of code (you lose all the form-based events, even Me.Dirty no longer works). But you'll still have slowness retrieving the record and saving it -- there is simply...

Whoever is getting rid of your terminal server is a complete idiot. Try to convince the powers that be that it's a foolish decision. It doesn't have to be Citrix, which is more expensive and complex than plain-vanilla Windows Terminal Server. If there's no hope there (as there so often is with...

What has actually been partially re-invented here in this thread is referred to as Levenshtein Distance. Here's an explanation of it and a VB implementation, easily adaptable to Access: http://www.merriampark.com/ld.htm It's also implemented in VBA as Simil(). It can also be useful in...

You might want to study Allen Browne's solution to the problem: http://allenbrowne.com/appevent.html You might try to come up with a list of pros/cons for his approach (though I don't really know any other), since you'd basically be cribbing someone else's answer otherwise.

I have always thought that MS's sample databases and templates are really very badly engineered from the standpoint of best practices. I've never understood it, myself.

You did write this: I don't think either of your major premises the is strictly true. Loss of data from conflicts is not very common at all -- indeed, you have to ignore your conflict resolution in order to lose data. That is, in any synch, Jet resolves the conflict, and one edit wins. Then...

With all the users on the local LAN, there is no reason to use anything other than linked tables from the front-end MDB/ACCDB (forms/reports/queries/modules/etc.) to the back-end MDB/ACCDB (tables only). Each user has a front end on his or her workstation and there is a single shared back end...

Replication works fine with synchs across a VPN if you use INDIRECT replication. However, that is much hard to set up and maintain that plain vaniall DIRECT replication (the kind you get from the Access UI). See the Jet Replication Wiki for everything you always wanted to know about Jet...

@HiTechCoach: Where do you get the idea that Jet replication is not suitable for updates in multiple locations? It definitely is, though it can cause problems if you have certain kinds of updates. For instance, a single record updated in multiple locations is going to be a problem, but I have a...

Yes, but you might want to retain internal single occurences of double quotes. My suggestion leaves those alone.