Search results

Might I ask why you are copying to local hard drive?

Perhaps I should have not said that as I skipped over Access XP (2002). My experience has been in 97, 2000, and 2003. I do know though that you can experience reference issues when opening an 03 database with 2000. The application designed in 03 can have references to libraries that were not in...

Access has never been backwards compatible, only forwards. This means 02 will not open 03 DB's but 03 will open 02's. When designing your DB, find the oldest version of Access that your users have and build with that version. Either that or upgrade all of your users.... Create your .mde with...

I would suggest making a backup NOW if you have not done so. Then implement some plan to make regular backups in the future.

I really dont have a definate answer for you but you may try a couple of things. Check your server and see if you can configure the mime type. Also, you could try using a Word document instead of an HTML page. That may do the trick.

Try this: objAccess.Quit Set objAccess = Nothing

What is the code you are using? Try creating a new command button using the wizard and tell it to close the form.

1) you will see linked tables in the FE. The actual tables reside in the BE though 2)no 3)yes 4)yes 5)yes Any editing or changing of the program will have to be done with the .mdb. Then you will create a new .mde and replace the old one. Make sure you save the .mdb! Split first then make...

Me.Refresh

Zip it with WinZip first and send it in .zip format

Both the FE and the BE will have .mdb file extensions. It is advisible to make the FE an .mde file though for increased security. That feature can be found in the tools menu too. Edit: I also would suggest doing a search here on the forum. There is a wealth of knowledge and whatever questions...

Tools/Database Utilities/Database splitter That is where you will find the utility to split your .mdb into a FE/BE. Once this is done the 2 halves will talk to each other via linked tables. After placing the BE on the server or folder you may have to relink the tables due to the change of...

You will need a front end/Back end set up. Once your application is done, access provides you with a utility to split the DB. The FE contains all the forms for the users to manipulate the data and the BE contains the tables that store the data. They talk to each other through linked tables...

This will close the switchboard and open it again which will return you to the primary page. Change the terms to suit your application: Private Sub Command2_Click() On Error GoTo Err_Command2_Click 'closes the switchboard DoCmd.Close acForm, "Switchboard"...

Well I guess I am not sure how switchboards work since I never use them. I think you will find that most people here will advise you to stay away from them and make your own out of forms that you can make look and act anyway that you want them to. I will have a look at switchboards though and...

One trick you can try.... create a command button that closes the form you are trying to close. Copy the code that makes it work and paste it where you need it such as the onclose event of a form :D

There are a few ways to go about this but the best I have found: Paste this into a new module: Function fOSUserName() As String On Error GoTo fOSUserName_Err Dim lngLen As Long, lngX As Long Dim strUserName As String strUserName = String$(254, 0) lngLen = 255 lngX =...

Well, I can't quite figure out how you came across this as it is not the error that you were having. None the less, I am glad that you got it sorted out. All you did was register the DLL and your trouble went away? 3 Cheers!

What is your OS? Edit: If this were me having this trouble for nearly a week, I would probably not be able to stand it. By now I would have low level formatted my disk and reinstalled all the software. I used to do this on a regular basis but since XP I find that it is not necessary as often...

The Front end (FE) will contain all of your forms for the end users to manipulate data with. The Back end (BE) will contain the tables that actually store the data. FE takes the form of an .mde and the BE remains a .mdb. Now you can create new FE .mde for updates and not disturb your data stored...