 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Forms Programming / May 2008Access 2007 On Open event error in mixed 2003/2007 replicated data
Help: I have a replicated databse that is used in both 2003 and 2007. Most development is done in 2003. I have stability problems with replicated/synchronised databases when running in 2007. The database normally opens with a switchboard menu, but on occassions the following error occurs:- "THE EXPRESSION ON OPEN YOU ENTERED AS THE EVENT PROPERTY SETTING PRODUCED THE FOLLOWING ERROR: OBJECT OR CLASS DOES NOT SUPPORT SET OF EVENTS". Once this happens the databse will not open. I have to create a new replica which may or may not work. The strange thing is that I can run the database failing in 2007 from another rmachine that is running 2003, so it seems that the problem is specfic running 2007. Any suggestions or help would be appreciated Are you replicating the entire application (i.e. the forms, reports, macros and modules)? Replication is only intended to be used on tables.  SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) > Help: > I have a replicated databse that is used in both 2003 and 2007. Most [quoted text clipped - 12 lines] > problem is specfic running 2007. Any suggestions or help would be > appreciated When going through the synchronise process it will exchange data changes and any design changes as it is only the MasterDesign database that can be modified, so if dessgn changes are reuqired they will have to be synchronised to the replicas as well. The databse is in a Beta_live state and eventually only data changes will be the norm, but at the moment there is still some ongoing design work. However it still doesn't explain why the database works ok then fails to work, but only in 2007. Thanks alalthwell > Are you replicating the entire application (i.e. the forms, reports, macros > and modules)? Replication is only intended to be used on tables. [quoted text clipped - 15 lines] > > problem is specfic running 2007. Any suggestions or help would be > > appreciated Yes, it will replicate design changes, but you shouldn't use it in that way. Your application should be split into a front-end (containing the queries, forms, reports, macros and modules), linked to a back-end (containing the tables and relations). Only the back-end should be replicated. To get changes in the front-end to each user, simply replace their copy of the front-end. SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) > When going through the synchronise process it will exchange data changes > and [quoted text clipped - 34 lines] >> > problem is specfic running 2007. Any suggestions or help would be >> > appreciated Thanks for you message. I am not sure why splitting the database will solve the intermittent nature of the pronbelm I have. Also if I split the database how will the user be able to synchronise the replicated database that holds just the tables since the user will not have visibility of this database. The SynchroniseNow function is currently available on the toolbar when the user open their replicated database. If the user is opening a linked - not replicated - front end forms,queries, modules etc how can they sync the backend tables to the Master database. If it is possible and solves my problem then I will be very happy. I look forward to your reply. Regards alathwell > Yes, it will replicate design changes, but you shouldn't use it in that way. > [quoted text clipped - 42 lines] > >> > problem is specfic running 2007. Any suggestions or help would be > >> > appreciated No guarantees of course, but replicating application components is known to cause problems, so it's probable that splitting the application will help. All applications should be split, whether they're replicated or not. Presumably once the application is split, you'll be able to have users sharing the same back-end, so it won't be necessary for each user to be able to synch the back-end. SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) > Thanks for you message. I am not sure why splitting the database will > solve [quoted text clipped - 68 lines] >> >> > problem is specfic running 2007. Any suggestions or help would be >> >> > appreciated Thanks for the message. The reason I have not split the database is that the replicated copies will be used completely off any corporate network and often with no internat access either. The replicated copies are loaded on laptops where the nature of the business means people are working away regularly. If they could gain access to a single shared backend set of tables I would have splti the database, but they cannot. The fact is that the users use their copy in a very standalone fashion until they return to their corporate offices where they then onntect to the netowrk and go through a synchronisation process. This means I cannot split the database as I do not believe there is mechanism to synchronise the split backend tables only. In a split database scenario the user will only see the front user interface of the databse preventing access to any synchronisation of the backend tables. if what I am saying is incorrect please let me know how the user can sync the backend tables in a split replicated environment. If it is possible I will test a split setup. Regards alathwell > No guarantees of course, but replicating application components is known to > cause problems, so it's probable that splitting the application will help. [quoted text clipped - 76 lines] > >> >> > problem is specfic running 2007. Any suggestions or help would be > >> >> > appreciated > The reason I have not split the database is that the > replicated copies will be used completely off any corporate [quoted text clipped - 8 lines] > database as I do not believe there is mechanism to synchronise the > split backend tables only. This is where you are completely incorect. > In a > split database scenario the user will only see the front user > interface of the databse preventing access to any synchronisation > of the backend tables. No, linked tables will give access to the data. > if what I am saying is incorrect please let me know how the user > can sync the backend tables in a split replicated environment. If > it is possible I will test a split setup. All non-replicated apps should be split if they are multiple user. All replicated apps should be split no matter what, because front ends cannot be safely replicated. Here's code that checks the .Connect string of a linked table in a non-replicated front end to find the back end database that is to be synched with a remote replica: Dim strLocal As String Dim db As DAO.Database ' choose the name of a table in your front end linked to BE replica strLocal = Mid(CurrentDB.TableDefs("tblPerson").Connect, 11) Set db = DBEngine.OpenDatabase(strLocal) db.Synchronize "\\Server\Database\RemoteReplica.mdb" db.Close Set db = Nothing Now, there are a whole boatload of other issues you ought to be worrying about (is the remote replica accessible? were there conflicts produced by the synch?), but that gets the job done. SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ Thank you for your message and help, I have succesfully implemented what you suggested, and it works really well with the exception of when I am running the solution on a machine using Access 2007. I have implemeted the changes in 2003 and all machines running Access 2003 work fine. When running the split/backend replicated copies in Access 2007 I get two errors: one when the Switcboard opens and only this happens when it first runs the error is :- 'Your Microsoft Office Access database or project contains a missing or broken reference to the file 'OWC11.DLL' version 1.0.' and the following error ocurrs when running the sync code:- Compile error: Can't find project or library The code stops on the Mid function replica strLocal = Mid(CurrentDB.TableDefs("tblPerson").Connect, > 11) I assume this is all to do with differences between 2003 and 2007. I was planning to import the front end into 2007 rather that copying it. Let me know what you think or you have a better option. Thanks again for your help Regards alalthwell > > The reason I have not split the database is that the > > replicated copies will be used completely off any corporate [quoted text clipped - 45 lines] > worrying about (is the remote replica accessible? were there > conflicts produced by the synch?), but that gets the job done. > When running the split/backend replicated copies in Access 2007 I > get two errors: > one when the Switcboard opens and only this happens when it first > runs the error is :- > 'Your Microsoft Office Access database or project contains a > missing or broken reference to the file 'OWC11.DLL' version 1.0.' This has nothing at all to do with replication -- it's just a garden-variety reference problem. Do you need that library? If not, remove it. If you *do* believe you need it, I'd question why, as it usually doesn't provide any functionality that is not available via other methods (usually with late binding, which avoids reference problems). SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ Thanks for your message. You are probably quite correct. I am not quite sure however, how to choose and remove the correct library entry. I can see in the VBA tools reference area there are several library types (assuming this is the right place to look) which one should I remove. If I remove this from just the one main design copy will that be enough for all of the distrubuted copies I will need to create. Regards alathwell > > When running the split/backend replicated copies in Access 2007 I > > get two errors: [quoted text clipped - 10 lines] > functionality that is not available via other methods (usually with > late binding, which avoids reference problems). When you go through Tools | References and click on each of the selected references (the ones at the top of the list with check marks in front of them) in turn, the specific file is displayed in the bottom of the dialog. SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) > Thanks for your message. > [quoted text clipped - 25 lines] >> functionality that is not available via other methods (usually with >> late binding, which avoids reference problems). > I am not sure why splitting the database will solve > the intermittent nature of the pronbelm I have. It may not, but it's the most obvious thing to fix, as YOU'RE MIS-USING JET REPLICATION. Eliminate that problem, and either your issue will go away, or we can look at some other cause of the problem. SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.