Search results

I'm sorry! I don't know why I bother getting up some mornings!!!! I was using one of my production workgroups whilst creating your demo! So yeah it was secured! Try this instead!!!!! ;)

Sorry, suppose the code is a bit much if your starting out!!!! Ok Ive created a quick example databas for you.. Open the database and then open the form. There are a number of controls on there that basically just control all the options that the function has available. Ive added a combo...

Good work batman! That should sort it!

Does someone have the code to return the current version of office or outlook? I have found application.version but this dont work in 97. Or even better would be to tell me if cretain security patches had been added to Oulook exchange servers? Cheers

Oh I see. I think!! No, you should paste the code into a new module. Then from each button you can call the function passing in the each recordset you want to export. Does that answer the question?

If you are going to export 10 times then you should probably keep Excel open until the last export to save time. You can do this by using the blnCloseAfterExport option and only setting this to true after you last export. But you would have to create 10 different recordsets and call the...

I'm not sure why your not being prompted to enter a username.... Ive just tried this on my XP test machine, opening a 97 db on XP but without joining the correct workgroup... It prompts me for my userid but then tells me that I'd don't have permissions.. All I can suggest is to open the...

There is no need to remove the security from your database to convert it!!!!!! I'm currently going through the exact same problem at the moment... Business migrating from Win NT and Office 97 to Win 2000 and Office 2002. When you open a 97 format Databas in Office XP or 2000, the first thing...

Access security! You need to impliment Access security and create different accounts for each use that will use your system. For each user you can then grant permissions etc that allow them to do certain things, edit queries for example or in your case not being able to edit queries. Have a...

Theres a few parts to this request.... Firstly Create your ID field in your table and set the Indexed property of the field to "Yes (No Duplicates)" this then stops a number being entered twice. You can also set the number to "Autonumber". Access will then generate a new number for every new...

Actually an easier way has just sprung to mind.... dlookup("Name", "MSysObjects", "Name = 'LEAFile") if dlookup finds the table it will return a string containing LEAFile if not it will be null Cheers:)

Hi just add the following whenever you reference a string etc that may have a qoute, single or double... chr(34) & "Test's out OK" & chr(34)) The chr(34) returns a " So you code would look like.... Mytarget = "[MyField] = " & chr(34) & MyTextBox & chr(34) If IsNull(DLookup("[MyField]"...

Ok heres the code for ya... There are 2 functions.. fExportToExcel - This creates an Excel export fOpenApplication - This opens an instance of an application To use copy and paste the 2 functions into your db. Then create a recordset object that contains the data you wish to export. The...

I'm guessing you want to check in Access right? well if so, you got two ways I can think of off the top of my head.... First up, similar to your method but query Access sys table instead, so... SELECT MSysObjects.Name FROM MSysObjects WHERE (((MSysObjects.Name)="table8")) You can then use...

As you know Excel can only take 65,000 rows per sheet and unfortunately there is no built in method of splitting out your data accross seperate sheets. So you need to do it yourself!!!! You'll probably have to create 2 or more recordset objects that break down your data into easier to use...

Hi! unfortunatly not as simple as Excel (Using application.ontime) but still fairly straightforward. There are actually two ways to do this, which one you choose will depend upon your needs... The first method is to have the database running all day long. When the database opens, you open a...

You could use a DSUM function to do this, pretty straightforward just have a look in the help file. :)

Modify the recordsource in Combo27 (Nice name!) so that it brings back the information for you. Then you can reference it by pointing to Combo27.column(2) or whatever you column your query returns it to.

Hi IgorB in the code I pasted, in function fCreate_DSN there is a bit.... lngResult = SQLConfigDataSource(0, _ ODBC_ADD_SYS_DSN, _ "SQL Server", _ "DSN=" & strDSN & Chr(0) & _ "Server=" & strServer & Chr(0) & _ "Database=" & strdb & Chr(0) & _ "UseProcForPrepare=Yes" & Chr(0) & _...

Sorry I can't help you with the batch file, but I intreuged as to why you would want to do that anyway? Surely when you bring it in to Access it will be appended anyway?