Recent content by Shado

I can't recall off the top of my head sorry (multi projects going on). If I recall correctly, there was a reference to the forms load event somewhere that fired as the current form was closing.. Hence the infinite loop which caused the issue.

It's fixed. Was a logical error on the old programmers part (I've taken over the project). I couldn't have uploaded it though sorry, it's linked to an internal SQL server.

That's what I thought also. Which is why it makes no sense. Back to the drawing board I guess!

Hi all, Is there a way to tell if the user has pressed the exit button on Access itself? (The red cross in the top right corner). I've run into an issue where if the user hits this button, the currently open form fires form_load which in turn is opening a dialog box. Due to the dialog box...

Sure can. Simply save it as an .mde file. I know how to do it in Access 2010, one would assume it'd be different. However, it's under the Save As option in 2010.

The syntax for Iif is: iif(Expression, True Result, False Result) Your last iif only seems to have a True Result but not a false? Feel free to correct me if I'm being blind again :D

Hi Rod, Thanks for the reply. Sadly, nobody seems to be able to answer this. Guess it's back to the drawing board!

Hi all, Unsure if this was the correct place to post this but here goes... Essentially, I'm using an Access frontend to SQL server backend. I'm wanting to make it so that if I open record 2301 for example, and Joe Bloggs also opens this record, only I can edit it. I've been playing with SQL...

Use views. They operate the same as tables. Working on a similar situation at present.

Hi all, I'm using BCP to write a querys result to a text file. This works well except there's a business requirement that I use no delimiter between each field... So the output is based purely on column size. Current output example: When it needs to output similar to this: The software...

Try: SQL = SQL & " where item = Like '" & Combo62 & "%'" As for the dates, remember SQL likes to Americanize it.. It's YYYY-MM-DD.

Weather great.. How bout there?

Put a bit datatype'd field that decides if the records old or new? What technology are you moving the backend to? SQL Server?

Look into sending messages via Outlook. By far the easiest method and it works a treat. If I were at work I could paste you some code. I think it's a similar format to your current code though.

Or, you can get a 60 day trial from the Microsoft website. :)