Me and my colleague are working on an ms access 2007 based application.(Th e database is sql server 2005)It is all about making certain changes on the application by creating some sub forms, forms or just adding a grid or a button to the old one.We have divided our work and plan to merge them later.Since both of us are new to access we do not know how to merge our works(we are working on different servers).Shall I simply copy and paste his work into mine?HOW?Or is there a better way of doing it?
-
-
I'm afraid there's no easy answer to that one. Working together on such a project can mean 101 different things. All I can suggest is that you make clear notes of all you change then discuss how the merging can be accomplished when you both understand the changes that are involved. -
every change to be made has been documented.The only thing that is troubling us is how to combine them so as to get the final application without affecting the macros and other forms.Comment
-
I can only repeat myself :-
Originally posted by NeoPaComment
-
Just an idea:
Work each one on a different FE (Front End database) and to different parts using the same BE (Back End database).
When one of you have finish a part, the other one can import that part (a form, a query, a module, a report) in his FE. This way you (both) will have all the time a general view. Also you have a kind of back-up.
It is ONLY an idea. Because, as NeoPa point, there are a lot of things to think to.
Good luck !Comment
-
That could certainly work as far as it goes. There are parts of a database that wouldn't fit within that description though. That is why I suggested what I did. It certainly seems a solid, fundamental approach though Mihail :-).Comment
-
Hy NeoPa !
This is a chat post so I think you remove it after you reed, but not necessary.
As far as I know (and this time is very very far), they can't finish the job if they don't start it.
On my keyboard the DELETE key is more useful than the ENTER key :)) .
And I am sure that this is the situation for many other coders more or less skilled.
So my advice for HiGu and his co-worker is to start the job. Now ! :))Comment
-
Sounds like a promising idea.Both of us are actually using the same backend database but different front end. I hope we can also import subforms. Need to check that. Thanks a lot!Comment
-
Forms, Reports, Tables, Data, Queries. These are all importable from one database to another. Forms and reports also have the facility of exporting to the file system. This means that they can even be copied and sent via email for instance should that be required.Comment
-
So, I guess I need to delete the old forms and import the new forms in which changes have been made. Will that not affect the forms' relationship with other forms in the application? If it will, then we need to study the relationship of all the forms with each other.Herculian task.There are around 60 forms and some 15 reports.Comment
-
The relationship are established between tables in the BE database. Not between forms. So I don't see any problem here.
Do not forget to make copies to both databases before start.
Good luck !Comment
-
What about relationship between a form and a subform?If I import a subform then how would I link it to the relevant form? I'm talking about Link child field and Link Master field.Comment
-
The sub-forms ARE forms.
You can see that in the tree manager: No difference between them.
More, maybe you know that you can design a "stand alone" form (I am not sure that is in true English what I say) and use it as a sub-form.
So, as long as you have both, main form and the sub-form, in the same database, Access will do the job without your intervention.
But is no need to ask every time.
The computer will not become angry if you try something wrong.Comment
-
Between the form and the sub-form is not a relationship. Is hard for my English to describe why. It is hard even in my mother language because I am also a beginner in databases. Bu I know that i am right. Maybe someone else will enlighten you (and me too).Comment
-
The relationship between one form and another, which appears on the first as a subform, is defined within the subform control and is a simple name reference.
IE. If form [frmA] has a Subform called [sfmB] then [sfmB] might have a Source Object property of "frmB". If [frmB] is replaced in the database then the new version of [frmB] will be loaded into [sfmB] on [frmA] in place of the old version.Comment
Comment