replicated & non-replicated tables

[pkstormy]

David,

Here's a few key working examples of mine within the link above (must have 2000 or 2003/XP, (not 97). You might find them interesting:

http://www.dbforums.com/6274786-post19.html (script to prevent locked *.ldb files from EVER happening - you can 100's of users using the same application!)
http://www.dbforums.com/6274790-post20.html (getuser() method - retrieve login automatically)
http://www.dbforums.com/6274791-post21.html (reporting and exporting)
http://www.dbforums.com/6274795-post23.html (dice and cycling game)
http://www.dbforums.com/6274796-post24.html (sample import routine)
http://www.dbforums.com/6274797-post25.html (for fun)
http://www.dbforums.com/6274798-post26.html (for fun) - visual basic games I created that are challenging and fun.
http://www.dbforums.com/6274809-post27.html (alphabetical searching)
http://www.dbforums.com/6274874-post30.html (popup Calendar Example)
http://www.dbforums.com/6282462-post36.html (reporting example)
http://www.dbforums.com/6289596-post39.html (another search example)
http://www.dbforums.com/6291638-post40.html (search/storing file names.)
http://www.dbforums.com/6294427-post42.html (Find out who's in an mdb)
http://www.dbforums.com/6301669-post51.html (nice form manipulation - make a form oval, full screen, translucent, etc...)
http://www.dbforums.com/6304815-post55.html (reporting with progress bar)
http://www.dbforums.com/6305980-post57.html (some cool buttons)
http://www.dbforums.com/6310284-post59.html (form coloring)
http://www.dbforums.com/6332819-post68.html (login/permission system example)
http://www.dbforums.com/6351157-post71.html (MSAccess jeopardy)
http://www.dbforums.com/6390529-post84.html (never create another MSAccess report again!!! - my favorite)
http://www.dbforums.com/6405612-post88.html (dragndrop tweaked from Allen browne)
http://www.dbforums.com/6426828-post91.html (find login/password from any mdw file)
http://www.dbforums.com/6433357-post94.html (import all xls files in a folder into an mdb automatically)
http://www.dbforums.com/6452958-post100.html (unbound form design)
http://www.dbforums.com/6459380-post103.html (color transition)

There's a few others in the link in the last post along with a 'best practices' section on form design and other things (pages 6-7). Feel free to critique any of them from the dbforums code bank.

 

[dfenton]

You're the one who brought up the issue of code, not me, so if there's an ego problem, it isn't mine!

I have nothing to say about any of your comments. You clearly aren't equipped to be making recommendations on the subject of Jet replication, because you had bad experiences 10 years ago because you didn't learn how to implement Jet replication correctly in the environment you were working in. And you appear never to have bothered to learn what you didn't know then. Thus, your advice on Jet replication is of little to no value.

Your posts, in fact, are self-refuting -- anyone can read them and tell from the conten that you just don't know what you're talking about.

As to supposedly recommending replication in all situations, this is a misrepresentation on your part. I'm not going to cite chapter and verse, but I always recommend against replication whenever there are better solutions. For the simple case of laptop users who need to edit data disconnected while in the field and synch back with the server upon return to the home office, Jet replication works really well with very little in the way of challenges in implementation, setup or maintenance.

However, with Access 2010 and Sharepoint 2010 with Access Services on the way very soon, I'll be citing that as the preferred method for supporting disconnected users. But that won't always be appropriate (e.g., if you don't have the resources to run a Sharepoint server, or aren't planning to upgrade to A2010 any time soon), so Jet replication will still have a place.

For fixed remote offices, I've been recommending against Jet replication in favor of Windows Terminal for quite a while now (since Windows 2000 Server and later were widely deployed), so I really think the assertion that I've been recommending Jet replication everywhere is unfounded.