Search results for query: *

You do not need to add any VBA code to your progam to use Wise or Sagkey. Sagekey takes care of it all. Sagekey is just a bunch of Wise scripts that will install your application along with the Access runtime and setup your application to run in runtime mode. This includes creating special...

I would highly reccomend Sagekey. However it dose require Wise or InstallShield installation system. I would reccomend Wise, it's very easy to use. I have had about 4000 installations using Wise and Sagekey and have had no Access related products. Sagekey lets you install your Access application...

This is very easy to do and is much better than using the Tab control. I use this method all the time. You need to place a subform on the main form using the wizard. This should be the default subform you want displayed when the main form is opened. Size the subform control how you want an give...

I gave up on the Microsoft package and setup thing a long time ago. I now use Wise Installation standard and Sagekey Acess 2000 Runtime scripts. This is the only way to distribute an Access application without any headaches. This allows you to combine the Access runtime installation with your...

By the way Replication IDs are not Long Integers. Below is a sample Replication ID {0005AEC1-9408-4EBE-B733-81F9C6E3BD3F} Dermot

An MDE file is the best solution, but you must have error handling otherwise if the user gets an error, your application will crash. You should have error handling regardless of how you distribute the database. If you are using Access 2000 it has a wizard that can add basic error handling to the...

This wil open the report in preview mode then bring up the print dialog so they can choose a printer and set other options. When the click the OK button the report will print and then close. DoCmd.OpenReport stDocName, acViewPreview, , stLinkCriteria DoCmd.RunCommand acCmdPrint DoCmd.Close...

Your declaring your rst as a recordset and then you are setting it to nothing. Your then trying to open it but it does not exist. dim rst as new adodb.recordset set rst = nothing This is how your code should look. *********************************************************** Dim cnn As...

This is easy. Just add a text box to your detail section. Set it's control source to =1 and set the Running Sum property to Over Group. Just make sure the records are sorted by Rank. That's it, your done. Dermot

I think it should be set cnn = currentproject.connection = not as Dermot

Just put one subform on your main form and then change the SourceObject property depending on what the user enters. When you put the sub form on the main form give it a name like SubFormHolder. Remember this is not the actual name of the subform just the name of the sub form control that...

It should work fine with an autonumber. I mean that's why you use an autonumber, to make each record unique and so you can easily find records. If you use the button wizard to create your btnShowRecord button on your frmGoToRecordDialog form, it will generate the following code which works...

This might be what you need and it's free. http://www.mile50.com/access/rfil/index.htm Dermot

Forget about security and shift keys, just make your db into an MDE file. Users cannot make any design changes to an MDE. Give your users the MDE file and you keep the MDB file. If you need to make changes just make them to the MDB and then create a new MDE file. Dermot

Try cbo.Locked = True This will stop them from changing it but it won't be greyed out. Dermot

My previous post had an error, sorry. Put this in the Control Source of the text box. DlookUp("[ClaimID]","Claim","[ClientID]="&[Forms]![ClaimClient_MainForm]![ClientID]) Dermot

I would forget the query and use a Dlookup Put this in the Control Source of the text box. DlookUp("[ClaimID]","Claim","[ClientID]="&)=[Forms]![ClaimClient_MainForm]![ClientID]) Hope this helps Dermot

If you are looking for a tool to update the BE then check out this http://www.bwbf.net/dbupgrader/Default.htm Now this is a dream come true. It can update a backend database without effecting the data. You can add new tabels, new fields, rename tables, rename fields, change relationships, add...

You cannot not format individual words in a text box. You will need to use a Rich Edit control. I use Total Access Memo from FMS. It works very well but it's not cheap. http://www.fmsinc.com/Products/memo/index.html Dermot

Use the NZ Function. Nz([YourField],"Other") Dermot