DataBase - Make an mdb replicable via DAO in A07
Asked By Chris V.
06-Oct-09 05:11 PM
Hi newsgroup
The following code works fine in A03 to create a new replication master:
Dim ws As DAO.Workspace
Dim db As DAO.Database
Dim prp As DAO.Property
Set ws = DBEngine(0)
Set db = ws.CreateDatabase("d:\Master.mdb", dbLangGeneral, dbVersion40)
Set prp = db.CreateProperty("Replicable", dbText, "T")
db.Properties.Append prp
db.Close
But it fails in A07 at the line:
db.Properties.Append prp
with Error 3251: Operation is not supported for this type of object
I tried:
Set prp = db.CreateProperty("ReplicableBool", dbBool, True)
which should be equivalent, but gives the same error.
I also tried other version numbers instead of dbVersion40 (30, 20, ...) with
no success.
Please do not answer that A07 does not support replication. It should for
mdb's, it only does not for accdb's.
I am working with A07 (12.0.6423.1000) SP2 MSO (12.0.6425.1000)
Can anybody help me? I would appreciate very much!
Thank you.
Q2hyaXMgVi4
(1)
Database
(1)
DBEngine
(1)
ReplicableBool
(1)
DbLangGeneral
(1)
DavidThank
(1)
ChrisV
(1)
DbVersion40
(1)
David W. Fenton replied to Chris V.

This sounds suspiciously like the bug in DAO synchronization in the
original shipping version of A2007. It was fixed in SP1. Perhaps it
has reverted?
I do not use A2007 (though I just downloaded O2007 via MSDN so I can
start working with it), so I cannot test your code myself.
Have you gone through the Object Browser in A2007 and checked that
there are not different objects in teh new version of DAO? I have
reviewed it in A2003, and note that there are a number of new
properties that are designed to account for the differences between
plain old Jet 4 and the new ACE features. For instance, from outside
A2007, there are two Field types/Field, Field and Field2. If you
examine the properties/methods of Field2, you will see that it is the
same as the traditional Field object type, but extended to support
new field types in the ACE, such as Attachments and Multivalue
fields.
While I would not expect what you are doing to cause a problem,
perhaps there are some differences there in the database properties
data type or in the properties collection that are causing the
problem.
I know it is a long shot, but it is a place to look.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Chris V. replied to David W. Fenton
Hi David
Thank you for your help. I must admit that it was not helpfull directly, but
indirectly by knowing that there is somebody out there believing there could
be a solution. I must also admit, that I was not quite correct in my
description of the problem. In fact the code works fine if I use the
parameter dbVersion40 to create a mdb file in format A02-A03. As I was
debuging for hours already I thought I had tested it this way, but obviously
I was not.
So for users that get the same error in A07: Make sure to use an mdb file in
the format of A02-A03 and do not try it with a format of A00!
Cheers
David W. Fenton replied to Chris V.
Er, what? You mean A2007? Or A2000?
Have you tested it with an A2007-format MDB?
It really ought to work with all versions, though.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Library Database DataBase Firstly, I am not sure if Library database is the correct term. I am talking about Dbs to which you set a reference drew blanks last time. Now assuming I have several referenced (library?) databases in my main database, how do I get the names of all the forms in all the Dbs? CodeProject AllForms.Count gives me the correct number of forms if I am in that referenced database. What I think I need is a method of looping through all the different CodeProject names in the main database, but there is not a sort of CodeProjects parent object. Or somehow moving the focus And, No, there is not any parent object for all the code projects. Because each database only knows about its own objects (or documents), you have to use a procedure in each database to refer to the objects in that database. E.g. to open a form in
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a couple of Excel spreadsheets that my little company uses (5 staff) into an all encompasing Access database and I was planning on splitting the database when I was finished to allow simaltaneous use of it by staff on our small to me that I am going to need to give staff access to this new database from remote locations (outside of our office network). Two staff members are regularly overseas, one been playing around with trying to link tables from remote locations (ftp path of the database on our Network Storage Device at the office) and needless to say - that do not It all started when I came across a very encouraging article on keeping your Access database as your front end application and linking to SQL Server database tables. I am finding it MUCH more complicated than I had hoped. Can anyone suggest a simpler way of achieving remote access to my database? I have at my disposal a Network Storage Device which has remote access capabilities (this
Exporting Report from Access into PDF DataBase Hi everybody. I am hoping someone may be able to help me out. I have a database report that I want to export into PDF for each individual customer. Basically, I want time this source data changes. I am trying to work with Stephen Leban's A2000ReportToPDF database right now, but it is far more advanced than my puny range of code knowledge I am working with right now: Dim qdf As DAO.QueryDef Dim dbs As DAO.Database Dim rstMgr As DAO.Recordset, rstMgr1 As DAO.Recordset Dim strSQL As String, strTemp As Close strTemp = strQName ' * ** code to set strSQL needs to be changed to conform to your ' * ** database design - - ManagerID and EmployeesTable need to ' * ** be changed to your table and field names ' Get rstMgr.EOF = False ' * ** code to set strMgr needs to be changed to conform to your ' * ** database design - - ManagerNameField, ManagersTable, and ' * ** ManagerID need to be changed to your table and field names Acct#", "Customers_To_Email", _ ' * ** code to set strSQL needs to be changed to conform to your ' * ** database design - - ManagerID and EmployeesTable need to ' * ** be changed to your table and field names strSQL everybody. I am hoping someone may be able to help me out. I have a database report that I want to export into PDF for each individual customer. Basically, I want
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load suited to handle databases beyond stamp collection size and lacks most features of a "real" database management system. Consider using a relational database, i.e. SQL Server Express, its free. Make sure to set primary key properties to to worry about problems like SQL injection attacks to you application. best, MiB. The JET database engine is often faster and more efficient than similar retrieval with SQL Server. And simply can be summed up as your general ignorance on the matter how = 20 computers and database engines function and operate in our industry. So your galactic stupidity and ignorance is well years - version 4 came with Office 2000. If JET is so vastly superior to regular database servers, kindly share the pearls of your wisdom and explain why companies like Oracle (guess rationale, but I am sure you will enlighten us. Can you also explain, please, why database client products like Sparxsystems Enterprise Architect using the same relational schema, same index structures, and to criticize an important MVP like you. Maybe this source is: http: / / databases.aspfaq.com / database / what-are-the-limitations-of-ms-acc = ess.html. I would like to humbly hint
Restated: "Fields are expensive, records are cheap" DataBase Hi, First let me apolozie for the empty question below. I hit the Post button multiple small rows versus one large row. And we are assuming a 3rd normal form database design. And it may well be that I am totally misinterpreting the ???Fields are expensive your comments. Dennis Access Tables DB Design Discussions Access 2007 (1) Oracle (1) VBA (1) Database (1) Report (1) MVFs (1) Sharepoint (1) Attributes (1) The mantra in the subject line is purely a rule-of-thumb for beginning database designers. It has no bearing on your question about data access. Your question revolves around use up 510 bytes (unicode) of disk space to store those 2 characters. Internally, the database keeps track of where each field starts in each record. Some fields (memo, OLE, attachments being faster to retrieve. There are many other factors at work here, including whether the database has been compacted recently, whether you are using page- or record-locking, whether the disk just for performance reasons. The management of those relationships alone represents unnecessary complexity for the database and for developer. You may be forced to go that route if you are subclassing thinking in posting.) Having said that, having 60 fields in one table is unusual. The database I happen to be working on right now has 93 tables, and none of them