My colleague and I decides to break the jobs into two, she design the GUI in MSAccess and I design the classes in MSAccess too. Now the problem is, we need to combine those files into a single file. How I can do that? Any help is highly appreciated
Assuming that the classes that you implemented are modules in an Access database, then you can import one user's work into the other user's database (doesn't matter whether you're moving the GUI or the code) with the import function. Up to and including Access 2003 you would right click on the list in the database window and choose Import. . . from the context menu.
Related
I have an access database that I have been using for a while. I have been meaning to split the database for a while but hesitant to. I have many forms that link to tables. VBA code that aid in the forms and creating reports from this access database. Sometimes the VBA code will have a dynamic query that changes on certain conditions and runs a DoCmd.RunSQL.
If I split the database will all my VBA code break down as it points to the tables within my database. Do they need to be pointed to the backend or pointing towards the linked table is enough. Will the split handle this by itself?
Let me know If I was clear enough. My main concern is my forms/VBA code will stop working.
Make a backup, go to meny Database Tools, locate the Split database wizard.
Run this, and you are done.
All,
I am using the SSMA console to migrate certain objects from an Access DB to SQL Server.
By default, the console LOADS all objects, but in fact I do not require all of them to be loaded, nor do they need to be converted and migrated.
I was wondering if it's possible to load only certain objects from a database instead of the entire database? If so, how can this be achieved?
I cannot find it in the documentation :(
https://msdn.microsoft.com/en-us/library/hh313064%28v=sql.110%29.aspx
Many thanks.
Simply expand the metadata explorer, and expand the database down to the table level. As the follow screen shot shows, you can select any table you choose.
Thus save the project, and use that as the project name when you up-size. I not looked at command line options, but specifying the project in question likly is an opiton if you not using the above GUI. So use the GUI to setup the project and select the tables you wish. You then use this project for the up-size.
So I have this project on access 2003. I am trying to create a relation diagram of the tables. I have found this webpage of Microsoft: http://office.microsoft.com/en-us/access-help/create-a-database-diagram-adp-HP003085405.aspx but I do not see any Database diagram option as I was supposed to see according to that article.
I am not even sure what they meant by Diagram window (I can see the list of tables, forms, queries and so on in a window, is that what they meant?). I have worked with DB diagram in access 2007 and 2010 but 2003 seems to be totally different.
And another question: is there any restriction in creating diagram on front-end/back-end application?
The solution to this problem was fairly simple. I just had to double click on my mdb file then hold down the shift key. That made the options visible. The rest was easy.
Sorry my question might not be clear. I saw one answer but I think that is too advanced for me to even understand.
That article is referring to what is called an ADP project. An ADP project is a specialized type of Access database that ONLY works with SQL server. Thus the article you reference would not apply to creating regular Access databases (that are not working with SQL server). Perhaps you can clear up if you are in fact using an ADP (Access Data Project). From your description it sounds like you are not.
As for the locating where you build the diagram and setup relatonahsips, it always in the back end (or the "same" database). I mean you could not have 5 different front ends link to a back each with different relationships settings. So the actually physical mdb (or accdb) file is where the relationships are setup and other systems from Excel, word or even a MS Access front end can only link to that data file – not set up relationships.
As for the diagram option missing? You should find the option under the menu option
Tools->relationships
I cannot see design view for forms or tables in the Services template ms access 2010.
In access options/options/current database/ the check boxes (enable layout view & enable design changes for tables in Datasheet view) are both greyed out.
My question is. How can I get into the tables in design mode?
have any idea ?
Any web objects do not have a Design View. Layout view should still be accessible, though, for forms and reports. Web objects are indicated by a globe in the icon representation of the object.
For web tables, you can only change the design in the datasheet view. Go to the last column in the datasheet view to add a new column. That's the only way to change stuff around in web tables.
I do hope that helps!
Have you copied the template to a suitable location after download and chosen Unblock from Right-Click->Properties? You can also check that the file is not read-only due to other causes.
Have you tried the old shift/open deal? Hold down the shift key, double click the file and keep holding shift until the file is completely opened.
Genius
Have you tried the old shift/open deal? Hold down the shift key, double click the file and keep holding shift until the file is completely opened.
If it doesn't have to be a "Web Database" there is a way.
Create a standard Blank database.
Right click each object (Table, Query, Report) and select Export to Access
Point it to your Blank database created in Step 1.
A. You'll have the option to export the table definition with or without the data.
I admit, it is a little tedious, and possibly could be scripted to make it easier for a lot of objects. I had a small number of objects so it only took about 15 minutes.
You can also create a new blank database and import all of the tables, queries reports etc from the old database. This is a lot faster and does the job.
If it's a Web Database:
1. The tables can be viewed in design view only by exporting to a standard access Database - or creating a standard database and importing all the tables (and relationships) in one hit.
2. The other objects (macros, forms, reports, queries) can't really be exported or imported as stated by Bobort earlier. The 'web view' doesn't allow design view (forms & reports) or sql view (queries) so it is quite restricting.
Hey guys I've written a little module/macro that helps our inventory department, they will need to run the module/macro a few times every month. They receive the databases from out in the field these are exported from some 3rd party inventory tracking system we have.
My question, is there any way to install this module/macro outside of the db file but still within access so that the inventory management team does not have to open vb editor, import the module, create a new macro, name it, set it up properly to execute the function?
The module/macro does not need to be changed for any new database that comes in.
Basically they need to be able to open any database received by the field and have this functionality in the module/macro available to them without having to set this. Is this possible?
You could look at my article for vb123.com:
Using Database Library Files in Your Access Application
The thinking there is that you can put access objects in a library file (still an mdb or mde file, or any of the new access file types) and then by just adding a reference to the file in your VBE project, you get that functionality made available to you.
It works with forms, reports, queries, classes, etc. To be honest, I haven't tried it with macros, but don't see a reason why it wouldn't work.
The beauty is that reusable functionality is packaged into one file, that is still just a plain old access file.
If you had the inclination, you could also write an access add in that basically calls your macro in the library.
We did this with a product for making dealing with SQL much easier in Access, and it has worked for years with Access installations all over the world. You can install the add in using a professional installation package such as wise installation, making it a pretty seamless experience for the end user of your macro. However, there is a considerable overhead in writing this kind of setup in a professional way. Depends on what your users need, I suppose.
Perhaps you are thinking of VBScript or a back-end, front-end set up?
You can use VBScript to perform actions on an Access database, through the Access object, with ADO and so on. The script can either accept command line input, request information, or run against any database in the current directory.
With back-end front-end, the new database becomes the back-end and the Access file with your macro is the front-end. Your macro should ask the user for the name of the back-end file and either use that with the Access object or link the tables, according to what is needed to be done.