The first is regarding splitting a database into 2 files, one for tables, and one for forms and queries. I have a database whose data will be accessed from about 4 computers, and almost never will this data be accessed concurrently. In that kind of situation, is it easier to just put the whole DB in a share and give each user a shortcut to it, or should I be splitting it and just putting the tables on the share?
Second question:
The option in Access 2007 to make the database an .accde file. From what I understand this just locks down the structure of the database so it can't be changed. Is this correct? Can it be edited by an admin once it's converted to this format, or does it just stay that way? I guess if it can't be edited, one could just keep a copy of the .mdb, modify that, then reconvert it to .accde.
Also, if I were to split my DB, would I first split and then convert to ACCDE, or the opposite?
In my frontend code, I include a table with a version #. In my backend, I also include a version table. The front end will compare wih back end, and if it's different, it will force to get the updated version that it's stored in the LAN.
However, I do not want the user to open the file directly from the LAN because it might cause slow performance problem if multi-user,etc.
So I want to implement a code to force the application to be open only from desktop.
So far, I have a strUsername which detect the user network environ. Then, it will check the application path to determine if it was opened from:
C:Users<strUsername>Desktop
If not, then an error message will prompt to alert the member to copy the file in the LAN and save on their desktop.
It works on my laptop, all fine. Today I didnthe test in my user desktop, but the message saying that the file has to be opened from desktop keep appearing.
I double check the user folder and the Username environ is (cd98) but the user folder was setup as "CD98" capital letter. Does that affect the coding?
How can I make my code to not distinguish between lower or upper case either for username and folder user as well?
I have created a database, with various forms, modules and tables. Cos this is to be used where I work I have created an ACCDE version. I can't get the original version to open so that I can make changes.
I have a working database which runs fine in accdb mode. But when i compile it and run the accde file I get the error "The expression you entered has a function name that XXDB nameXX cant' find."The problem is that the autoexec macro cannot find the VBA public function that is called with runcode command.
The accde file is running in the same folder as the accdb. It is a split database, I am only working on the Front End..I have tried, amongst others:
- Creating a new vba module and copying all the functions across
- Renaming the target function
- I reckoned there was a corruption somewhere, so I created a blank database and imported all the form/code/etc across from the broken version, which imported fine. The accdb ran but the compiled version failed again
I do not see the Make ACCDE button. I'm using Access 2010 32 bit. Have an ACCDB FE file which I'm trying to create the ACCDE. I've compiled and fixed the VB errors. I've review trusted sources and insured the folders are trusted. For whatever reason, the button is not showing.
I have an Access 2007 mydb.accdb file. If I click on it, it starts up fine. If I click on it again, then focus goes to the already open db.
If I do the same but with the .accde of the same db, for each click a new instance opens. This is not good, in that a single user then can have multiple instances running without noticing it, and that might mess things up. What Windows setting to use, to convince Win XP that only one instance of mydb.accde should run, similar to the .accdb?
I saved my front end db as .accde in order to distribute it without user being able to edit my objects. As it turned out, when I open the .accde now I see my code doesn't work anymore. I have a lot of startup code and now it doesn't trigger at startup. Basically all my forms use vba code and none of them works in .accde . Accdb version works without any issue.
I have created a database to track leave requests for staff. After upgrading from XP to Win7 and upgrading to Access 2010, some workstations will not run the ACCDE front end, but the ACCDB runs fine.
I am storing the front end ACCDE in C:Users\%username%appdataRoaming which is trusted - and I do not receive a warning for this. When the ACCDE loads I receive the message that "The database cannot be opened because the VBA project contained in it cannot be read.". I have tried running the application with different users to eliminate privilege issues. All the workstations are built from the same image and I cannot find any missing references or different patches. The workstations in question are running RUNTIME version.
I have checked for missing references in the dev version. I have compiled the database right before creating the ACCDE, finally I have run the app with the -DECOMPILE option.
Using Access 2010 32-bit. I have a report that contains a Graph Chart (class = MSGraph.Chart.8). The reports works fine using the uncompiled .accdb. When I compile to .accde, the report is not rendered...I get an empty report screen as though Access is going to produce the report and nothing happens. I have to terminate Access using the "X" at the top right.
Trying to lock down an application by saving as ACCDE file. Saves OK but when you load application none of the controls work. I.e. button clicks do not launch "Open Form" or " Print Report" commands.But in ACCDB format application works flawlessly.
When I tried on a different machine I get an error message that says too many Table IDs. Odd since I only have 3 forms, 3 tables and 3 reports. Lots of DoCmd's and switching between the 3 forms but not sure why this would create "too many Table IDs"?
I have a few hundred access databases all with the same tables and structure, and want to import all the data in a 'mother' database (which i created with the same tables and structure).
I am using a sub that feeds a string to another public sub as follows:
Code: Private Sub cmdImport_Click() Dim strFolder As String 'source folder path for import Dim strFile As String 'individual file path strFolder = GetFolder(Environ$("USERPROFILE") & "Documenti") If Len(strFolder) <= 1 Then Exit Sub
In an .ACCDE I want to store the column widths when user closes a datasheet form (or subform) so that when opening it anew, the widths are as previously set by user. I could store this data in a dedicated table ( and userID, for the multiuser db), but is there a smarter way? Some array/ dictionary/ whatever as database or form property?
I have a split Database into Back-End and Front-End. I want to hide the Access Customize Option in my Front-End. I have tried to make the Database ACCDE but the option still appears to Customize the Access Database.
I also want to know why is it that when i make a Database ACCDE - some of the codes are not working properly???
I've Saved an Access 2010 File as an .accde version that opens Ok however none of the buttons (eg; delete record, go to first record, next record) that I placed on the form work at all (the standard record selectors at the bottom of the form still work). All the buttons work fine in the .accdb version - only the .accde version that doesnt work...
I have created an accdb file and saved as an accde file. The accde file opens with a form with command buttons. But the commands buttons do not work with the accde file (they do work with the accdb file). How do I get them working.
I have made a database, splitted it and then made the front end as accde. After that I copied both Front end & back end files in a shared folder. It is working fine as long as I am using it from my computer, but when I go to the other computer and try to open the front end, it gives the message of Unrecognized format error. This problem is only with the accde file, all other files are opening except this.
I've created and tested my database. What step or steps do I take now to make it so it's a program that only shows the forms and menu's I created, not all the Tables, Queries etc and the formatting options? Is there a link that explains what to do step by step?
I saved my database as ACCDE file which is executable now the problem i am facing is i can't edit my database since i can not view it into design view.
Getting ready to split a DB. No security really needed... Only the ability for multiple users needed. From what I have read here so far it seems best to use a MDE file on the front end and MDB file on the back end. One question is still not answered... I guess I will find out when I load the front ends on different stations.. BUT... I would like to know what to expect. I am assuming that each computer that I load the front end on I will have to go through and link the backend. Correct? I read a MS Knowledge base article about a form to do this... Is this only possible if you use the "developers edition" ??? Whats the common method for this task? Thanks Curtis
I have created an application that uses all the 'normal' factors of an access app. My forms are triggered by events that initiate some vba code which executes and then does something. No big whoop, we are all doing this; but I am going freakin' insane keeping up with changes. The users are using this app in a "live" test enviroment and the changes/updates are coming in quicker than I can type. "This field is not right it should read like this" Well I can't change it until everyone gets out - they don't like this answer:D
I jumped in before thinking a few versions ahead and did not split the database :eek: I have read a lot of posts here and other sites and I can tell that I need to split this app but am a bit hesitant. From what I can gather I would have a Front-End - houses all my queries and forms Back-End - houses all my tables
I have a few modules, where would they need to go so that I can work on them independent of what my users are doing? I would give each user a copy of the FE or make it available via network drive; would I then keep a seperate copy of my FE to make changes? If yes, does this mean my modules would be in the FE? Can I split the db now that it has been in live production? What are some common errors that I should look for prior to? I tried to split the db one time before, but my drop down list box(s) on the forms would not work. They are controlled by a query, not any code. Error msg stated could not find xyz sorry I don't recall the exact error
I need the ability to change, work on and update at will AND NOT effect my users.
I have been reading a lot about splitting databases on this forum. I still have some questions. 1) Will the FE (Front End) still show the tables? 2) Will users still be able to edit the forms, reports, etc.? 3) Will my code be hidden 4) Will all the users have up to date data showing when they open the Database? 5) Can more than one person open and input data in the database at the same time?
I also want to make an MDE copy, do I split first or make the MDE and then split?
The whole point is the following: I want the people (maximum 10) that will be using this database to only be able to do enter and view data. They should be able to generate the reports but not create new reports. I only want ONE person to be able to edit the forms, code, and reports. How would I do this.
