devices99

Members
  • Content count

    42
  • Joined

  • Last visited

Community Reputation

0 Neutral

About devices99

  • Rank
    devices
  • Birthday

Profile Information

  • Gender
    Not Telling
  • Location
    England

FIleMaker Profile

  • FM Application
    14 Advanced
  • Platform
    Cross Platform
  • Skill Level
    Intermediate
  1. Ralph thank-you so much for such a helpful and considered reply in my hour of need (and not being offended by my use of the word "urgent") – it is much appreciated! I think a conversion app updater is the only way to go, I've exhausted all other possibilities. I'm happy to dump the container data, as we've moved away from those facilities in the last version anyway. Ralph, would you recommended using XML or a MER file as a backup/upgrade files from now on, as we never want to be caught out like this when the file formats change again. We have 5 older versions stretching back 4-5 years with different binding keys (it's a world wide project with hundreds of customers), so that is the other issue. Do you know if FM12 has the ability to import fp7 files without conversion (unlike FM14), as I was considering downgrading to this 12, but having only moved from 11 to 14, I didn't want to request the downgrade unless it was possible - and I've made use of many v14 features which possibly may not downgrade. Thanks again Ralph.
  2. I have a v11 Runtime that we are upgrading to v14 - it's used by hundreds of users across the country. They have a backup routine which exports all the data into FP7 files (we chose this format, as some of the tables have a small amount of user defined container data in older version, which we'll slowly phase out now), it saves each file as a .bak so it's easy for the user to know which files are the backups, mainly when the upgrade to a newer version. This has been fine over many updates/new versions which we've written over the past few years, our restore function imports the data back smoothly. Until now... Moving to v14 runtime is a massive headache due to the file format changes, as FM doesn't allow users to import data only from the older .fp7 file version (how thoughtful). I've written a sophisticated backup conversion routine, which takes the users set of fp7 backup files (named .bak files), and converts them to fmp12, it then removes the old files and renames the converted ones to the original .bak filename - so no changes are needed to our restore procedures. Written all natively in Filemaker using tricks with container fields to check files exist, and rename by exporting out again. This works perfectly in FMPA14, however it fails in the runtime with the error (each time trying when trying to convert an old backup file): "The file cannot be opened because it does not belong to this solution". Obviously I can't bind the backup files to the solution, as each and every users will be different. (It actually appears on a test, that the runtime doesn't even convert the files presumably because they 'don't belong to the solution') If it hadn't been for older versions with containers, I'd have just used a csv backup files and this problem wouldn't exist - however it does, and I urgently need some help! Any ideas and pointers gratefully received, 21 hours on it this weekend and counting!
  3. I've just removed the support in my custom installer so all users need Win 7 SP1 or higher now. Saves a lot of additional testing, and potential issues.
  4. Just at the same point as you Valdrin, anyone have any info on these multi-lang "WindowsUI.resources.dll" files - I assume these can be safely removed as long as you leave the "en" one (for english), however I haven't tested yet...
  5. Thanks Fitch, no emails in this solution so that hopefully won't be an issue. Will it run on Vista just unsupported, or is it blocked like version on the incorrect Mac OSes are? I have a custom installer so can weed out Vista if required, but happy to let users run at their own risk until they can upgrade to a higher OS.
  6. I'm just about to start converting a large v11 runtime solution to v14, it will be used at many end-user sites, with many different configs, ranging from a few Win Vista (I note this isn't covered by the system requirements of v14), Windows 7 (the majority), Windows 8/8.1 through to some testing Windows 10 (including older 32-bit and modern 64-bit OS installs). Are there any issues/problems to be aware of in v14; especially in consideration over v11 and with Runtime solutions? My v11 Runtime system is extremely stable, experiencing no issues over the past few years, which is testament to the design and FM version considering a large solution user base. I'm starting to upgrade as I phase out v11 as a development platform - which has proved to be very stable over the past 4 years. I was also hoping to find a good "bible" type detail book to refresh myself on the new v14 features, but there only seems to be a "missing manual" guide on v14 available from Amazon. Thanks in advance.
  7. I'm creating an update to a system which has several older versions, they are runtimes, each user backs up their data (into a special fp7 file) using an inbuilt script which saves various system settings in various fields, as well as other tables for their data. Everything is locked down, runtime kiosk. When they receive a new version they run a resoration procedure, which is a special import bringing in all their settings and data from the previous version's backup file: this could be v1 to v5, v2 to v5 etc. depending on their upgrade path. As the system has grown, new settings and features are of course added, and in newer versions I've added these to the backup, in this new version there are many new settings and defaults which will get backed up. Providing I always use a custom import order (not matching names) in the restoration script, if fields aren't found (e.g. when v2 is importing a v1 backup) presumably they'll just get ignored... Would there be any circumstances where the import would fail or the custom import order be changed if fields are missing? I've done various sets of testing and can't trip it up, but we are talking a large group of installed users and if there is any danger of error, I'd rather have separate import scripts for each of the new settings/feature sets. Thanks all. (11v03 advanced Win 7 pro)
  8. Get(LastError)=401 vs Get(FoundCount)=0 Is there any advantage/disadvantage to using either of these, when scripting and checking if a find returns no matching records? (Obviously I always test for the last error immediately after the find.) Could either ever be tripped up and give a wrong result? I've been using FM since the early days and have always tested against error 401, but in recent months I've started to convert a system and in new scipts I've been erring towards get(foundcount), perhaps for readability... (This particular system I'm working on is v11, and will be upgraded to v12 next year.)
  9. I've got exactly the same problem! FileMaker 11 runtime, created under XP, working fine, installer with Setup Factory, and under Vista / 7 there is a problem when users install, the files are read only (when users open the system, they can't enter a new record and so forth.) This is installed directly to the Program Files folder, which I understand is a protected folder under Vista and is causing the issue. So even though the user account has read/write access to the hard disc, and uses the UAC password/permission for installation afterwards the files in the new folder within Program files are read-only (which is useless!). Other than installing to another location, is there any other way to overcome this. Any pointers would be very useful. Thanks in advance.
  10. I've been working on a large system for over 12 months now, it's complex, but is working perfectly and is rolling out to users next month as a run-time. It has just under 70 TOs in the relationships graph, so it's not the easiest to separate. I've decided to now split the interface from the data to make user backups and upgrades more straightforward, as it'll be distributed into a runtime, and it'd be good to provide interface upgrades without having to import and export data. I've split small FMP systems with ease before, and massive ones in Access with a few mouse clicks, but this is causing a serious headache! I've split the data off (duplicated the original file), removed the tables from the interface and relinked all the TOs correctly in the interface to the new "data" file. Then I've removed all the layouts and scripts in the data file - all ok so far. But at this stage I have some filtered portals based on Cartesian and global variables relations which enable a user to show all records, or a set matching a criteria in a pop-up portal for a selection - this was instant before the separation - but now will only function if I add a full refresh cached joins to the on-enter event of the drop-down, is this normal? Deciding which TOs to remove from which file to clean it up is causing me the biggest issue. I was under the impression that only "interface based relationships" need to be in the interface file, but unless I'm applying that incorrectly (and it's been a 12 hour day so far with another 5 left, so it's likely!), every time I pick something to remove from the data side, it kills off functionality. But I don't want two sets of duplicate relationships in the data and interface, in case that causes a problem too. Finally, where should I store the value lists? I have some complex conditional lists and some relationships which reference value lists for filters, currently now I have a duplicate set in both! Advice appreciated as always :)
  11. I downloaded the demo from www.clevelandconsulting.com and it has a FMX plug-in: CC Pivot.fmx ... I was considering creating a report table, but exporting direct to Excel is far easier and cost effective for this version as the client fees aren't covering enough of my time for these extra features.
  12. Thanks to you both - always great info as usual! As you may have expected comment, I've got similar reports by date and by salesperson as you suggested, love your demo though in the other thread. I'm going to suggest at present they export the data to Excel and create a pivot in that, as they are very keen for the cross-tab view. If there was more money, I'd definitely look at that plug-in in detail, screen shots look superb bcooney - hope FileMaker Inc buys it and integrates the feature!
  13. I'm not at all sure how to approach this - whether with multiple portals on a layout, (if it'll give the result), creating a temp static table with the required data, or if there is a better / cleaner way? (FileMaker Pro 11) The data for the report is reasonably simple, key tables: tblSalesperson (SalespersonID, Name, Location, etc) tblSale (SaleID, SalespersonID, CustomerID, SaleTitle, Date, Amount etc - sales are flat single high level transactions, no multiline sales items required) I'd like to report the data grid / pivot table (similar to those in Excel) view, but obviously within Filemaker, not exporting the data out. Columns (across the top) need to be data driven from tblSalesperson: Salesperson1, Salesperson2, Salesperson3 etc. Rows, date based from tblSales, e.g: Quarter 1, Quarter 2, Quarter 3 and Quarter 4 (I've already calculated the quarters in a calc field in the tblSales. Then the data in the "cells" in this grid report will be the actual sales data from tblSales, usually several per person per quarter, only required to show the SaleID and SaleTitle in each "cell". Any pointers/tips? Many thanks in advance!
  14. Thanks bcooney, bit disappointed there are no direct syncing routines in Go - Syncing I agree is complex, I've written some mindbending VB and SQL routines in Access for subset syncing for offsite users for roaming systems. (Will review SyncDek from WorldSync.) So, if the ideal Go setup connects to Server (live), how is this catered for when people are out and about from the office - is it expected to put the Server on a secure internet connection and only allow live database access via Go like this, via a wi-fi, or use the 3G iPads only? Thanks!
  15. Completely new to Go, in fact I've only just started to read the pages on the FM website!! Don't even have an iPad to test it out on.... yet! I have a customer who doesn't use FM Server, but who is considering adding iPads for sales staff, so they can capture data with customers and return to base and upload the information. If we were to develop a FileMaker Go solution (probably a subset of their current main system), which captured customer details, orders etc. How can the data be integrated back (from 3 or 4 sales people on different iPads) to their main FileMaker system without using Server? Is it just a case of copying the data and having a script merge or are there more sophisticated options available in Go? Also for other larger customers using FM Server and Go on iPads, how does data connection/sync work? Do the iPads take a snapshot of the system out on the road, then sync back in the office? Is this automated or do you have to script/develop all the routines?